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

# Onboarding

{% tabs %}
{% tab title="Prerequisites" %}

1. An EVM wallet
   * If you do not have a supported wallet (e.g., Rabby, MetaMask, WalletConnect, Ledger), you can easily create one at <https://metamask.io/>.
   * After downloading the extension and creating a wallet, you must store your seed phrase in a private and secure location. If anyone else knows your seed phrase, they will be able to steal your funds.
2. Collateral
   * Supported assets such as USDT, USDC, WETH or WBTC
   * Gas tokens on a supported chain (ETH on Ethereum or Arbitrum, BNB on BSC, or AVAX on Avalanche)
     {% endtab %}

{% tab title="Step 1" %}

### **Connect a Wallet**

1. Open [VDEX](https://app.vdex.trade/)
2. Click **“Connect Wallet”** in the top-right corner
3. Select a supported wallet
4. Sign the connection request
   {% endtab %}

{% tab title="Step 2" %}

### Deposit Collateral

1. Click **“Deposit”**
2. Select a supported asset (e.g., USDT, USDC, WETH, WBTC)
3. Confirm **“Approve Funds”**

   <figure><img src="/files/DXpuNOiO5WxTtCdkHqDb" alt=""><figcaption></figcaption></figure>
4. Confirm **“Deposit Funds”**

   <figure><img src="/files/cTZSXpg12kZqpAUy6tAo" alt=""><figcaption></figcaption></figure>

&#x20;Your deposit will arrive within two minutes.

<mark style="color:$info;">Note: Depositing is a two-step process within your wallet. This is a blockchain feature.</mark>
{% endtab %}

{% tab title="Step 3" %}

### Start Trading

1. Below the VDEX logo, hover over the current trading pair (e.g. BTC-USD) and select your favorite asset&#x20;

   <figure><img src="/files/4HaL8NNsF5Sn8u3GD40O" alt=""><figcaption></figcaption></figure>
2. Select Buy or Sell and your leverage factor (e.g., 20x)

   <figure><img src="/files/TdQTdDv0jKED2JTO3eP6" alt=""><figcaption></figcaption></figure>
3. Enter your position size and hit **“Place Order”**
4. Monitor and close your positions

   <figure><img src="/files/e44B6XVIwbuBnMjSv4X8" alt=""><figcaption></figcaption></figure>

{% endtab %}

{% tab title="Step 4" %}

### Withdraw Funds

1. Click **“Withdraw”** below the order creation screen
2. Select the asset, blockchain and amount and click **“Create Withdrawal Proof”**

   <figure><img src="/files/DM4e0GhFNbcP5FR86YvC" alt=""><figcaption></figcaption></figure>
3. After 24 hours, click **“Validating Withdrawal Proofs”** then **“Withdraw”**

   <figure><img src="/files/EJGpUG8Wwdl9tSmfubaS" alt=""><figcaption></figcaption></figure>

<mark style="color:$info;">Note: To safeguard user funds during VDEX Beta, withdrawals are subject to a 24 hour delay.</mark>
{% endtab %}
{% endtabs %}


---

# 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.vdex.trade/trading/onboarding.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.