> For the complete documentation index, see [llms.txt](https://docs.hyperlink.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperlink.xyz/more/faq.md).

# FAQ

<details>

<summary>How does HyperLink relate to Hyperliquid?</summary>

HyperLink is a confidential trading layer **built on top of** Hyperliquid. The enclave routes your orders into Hyperliquid's order book, so you get Hyperliquid's liquidity and execution while your balances, positions, and open orders stay confidential. HyperLink mirrors Hyperliquid's API and EIP-712 signing, so existing Hyperliquid tooling works against it.

</details>

<details>

<summary>What stays confidential, and what is public?</summary>

| Confidential (inside the enclave)   | Public (on-chain on HyperCore) |
| ----------------------------------- | ------------------------------ |
| Balances and PnL                    | Deposit amounts                |
| Open positions                      | Withdrawal amounts             |
| Open orders, order and fill history |                                |

Only deposits and withdrawals are visible on-chain. See [Security](/security/security.md).

</details>

<details>

<summary>Can the HyperLink team see my trades?</summary>

No. The enclave is hardware-isolated; no one outside it can read your balances, positions, or orders, or extract keys. You can read your own state only with your own signature.

</details>

<details>

<summary>How do I know it runs the right code, and that my funds are backed?</summary>

The enclave publishes a measurement of the running code, and HyperLink commits reserve data on-chain. See [Security](/security/security.md).

</details>

<details>

<summary>Can I withdraw if HyperLink goes offline?</summary>

Yes. You can withdraw on-chain to your wallet if HyperLink goes offline. Funds are never trapped. See [Deposits & Withdrawals](/trade/deposits.md).

</details>

<details>

<summary>How long does a deposit take?</summary>

A deposit is credited once it is confirmed on HyperCore.

</details>

<details>

<summary>What are the minimums and fees?</summary>

There is no deposit fee. Deposits and withdrawals are gasless. See [Fees](/trade/fees.md) for current minimums and withdrawal fees.

</details>

<details>

<summary>Can I deposit any token?</summary>

No. Only allowlisted tokens can be deposited. The app shows the current set in the deposit dialog.

</details>

<details>

<summary>What does it cost, and how much leverage can I use?</summary>

HyperLink pools volume and staking benefits so users can access the lowest Hyperliquid trading fee rates available to the protocol. See [Fees](/trade/fees.md). Maximum leverage is **per-asset** and currently lower than Hyperliquid's [max margin tier](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/margin-tiers) for the same asset. See [Trading](/trade/trading.md) for how HyperLink differs from Hyperliquid.

</details>

<details>

<summary>How is auto-deleveraging (ADL) handled?</summary>

ADL follows Hyperliquid's priority: positions are deleveraged by profitability, highest unrealized ROE first. Your exposure matches trading Hyperliquid directly.

</details>

<details>

<summary>Can I trade both spot and perps?</summary>

Yes. Spot and DEX balances are separate; transfer between them using the `sendAsset` action.

</details>

<details>

<summary>Is there a HyperLink SDK?</summary>

No first-party SDK. Use a Hyperliquid SDK pointed at the HyperLink base URL for signed trading actions, and raw signed `/exchange` requests for private reads. See [SDKs](/api/sdks.md).

</details>

<details>

<summary>How do I create an API key?</summary>

An API key is an approved agent wallet. Create one in the web app (**Settings → API → Generate**) or with the `approveAgent` action. Agents can trade and query but cannot withdraw. See [Authentication & Keys](/api/api-keys.md).

</details>

***

**Related:** [Getting Started](/start/getting-started.md) · [Security](/security/security.md) · [Risks](/security/risks.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperlink.xyz/more/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.