Creating a deposit address
Deposit addresses can be created on the deposit page for each asset. The deposit pages for each asset can be reached from the main wallet page, which can be accessed by clicking the wallet icon in the Deribit user interface.
To go to the deposit page for an asset, click the "Deposit" button next to the relevant asset.
Once on the deposit page, a deposit address can be generated by clicking the 'Generate a deposit address' button.
Deposit addresses can be created on the main account and all subaccounts. Each subaccount will have its own deposit address, and any deposit made to the deposit address of a subaccount will be credited directly to that subaccount.
Important
For custody-enabled clients, the deposit process is different. Please contact custody@deribit.com for guidance. You can also review our Custody Options article.
Note
An account must have completed the verification process on the verification page before a deposit address can be generated.
Note
For Bitcoin, a new address can be generated every 24 hours.
For ERC20, Solana and XRP only one address can be generated.
Note
If an ERC20 address is generated, this address will be automatically added for every asset that uses ERC20 addresses.
Finding your deposit addresses, making a deposit
Deposit addresses can be found on the deposit page for each asset. The deposit pages for each asset can be reached from the main wallet page, which can be accessed by clicking the wallet icon in the Deribit user interface.
To go to the deposit page for an asset, click the Deposit button next to the relevant asset.
Warning
Make sure you deposit only on the supported protocols. Any deposit made on an incorrect protocol or chain might be unrecoverable.
Extra attention should be paid to which currency and network is being used. Not all networks are supported for all assets. The details will be mentioned on the deposit page for each asset.
Important
If a mistake occurs during the deposit process (e.g. sending unsupported coins or using the wrong network), Deribit provides a coin recovery service under specific conditions. For details, see our Coin Recovery article.
Supported protocols and confirmations
Deposit and withdrawal requirements & restrictions:
Unless otherwise indicated, do not use any wrapped tokens or alternative chains/protocols. Deribit may not be able to recover funds sent via methods not specifically mentioned on the deposit page of the specific asset in question.
|
Asset |
Supported protocols for deposits and withdrawals |
Required deposit confirmations |
Minimum withdrawal (without tx fee) |
Additional attention |
|---|---|---|---|---|
|
Binance Coin (BNB) |
• Binance Smart Chain |
1 |
0.0006 BNB |
|
|
Bitcoin (BTC) |
• Core / Legacy • Segwit (3 prefix) • Bech32 (bc1 prefix) • Taproot (bc1p prefix) |
1 |
0.00000548 BTC |
|
|
BlackRock USD Institutional Digital Liquidity Fund (BUIDL) |
• ERC20 only |
1 |
0.000001 BUIDL |
On-chain transfers require address whitelisting with Securitize (https://securitize.io/). |
|
Ethereum (ETH) |
• ERC20 only |
12 |
0.000001 ETH |
|
|
Staked Ethereum (stETH) |
• ERC20 only |
1 |
0.000001 stETH |
|
|
PAX Gold (PAXG) |
• ERC20 only |
1 |
0.001400PAXG |
|
|
Tether (USDT) |
• ERC20 only |
1 |
0.000001 USDT |
|
|
USD coin (USDC) |
• ERC20 only |
12 |
0.000001 USDC |
|
|
Ethena USDe (USDe) |
• ERC20 only |
1 |
0.000001 USDE |
|
|
USYC |
• ERC20 only |
1 |
3.538700USYC |
USYC can only be transferred on-chain to addresses that have been whitelisted with Hashnote. This includes withdrawals from the Deribit platform. The whitelisting process for private addresses is something that would be done directly with Hashnote, not on the Deribit website. For more detail on Hashnote and USYC, including the official documentation, visit Hashnote here: https://www.hashnote.com/ |
|
Solana (SOL) |
• Solana network only |
1 |
0.00000001 SOL |
Only deposit SOL. Do not deposit any other coin or token on the Solana chain. |
|
XRP |
• Ripple Network only |
1 |
0.000001 XRP |
If the sender does not support the XRPL format, the tag provided with the legacy address on the deposit page has to be included. Deposits without tags might be unrecoverable. Withdrawals for both XRPL and legacy addresses are supported. |
Deposit history
In the deposit history, all deposits will be shown. This table is presented per asset.
|
Field |
Description |
|---|---|
|
Address |
The Deribit address the deposit is made to |
|
Amount |
Amount in the relevant Asset |
|
Last update |
Date and time of last update of the deposit |
|
Status |
Either pending (awaiting confirmations or approval from Deribit) or complete |
|
Tx Info |
The transaction hash of the deposit |
|
Note |
A field to add personal notes to the deposit |
Deposit not credited
There are a few reasons why a deposit may not yet have been credited to an account.
-
Make sure the deposit is done on a supported protocol. If you have already sent funds using a protocol that is not mentioned on the deposit page for the deposited currency, you will need to contact support to see if it is possible to recover the funds. This recovery process can involve extra fees and a lengthy delay.
-
Make sure the deposit is confirmed on the blockchain with enough confirmations. Deposits are credited within a few minutes of reaching the required confirmations.
-
Check that you have added Originator details for the incoming transaction. This is done from the deposit page for the relevant currency, for example here for BTC.
-
The account receiving the deposit must have completed the verification process on the verification page in the main account.
-
Multiple deposits to the same address in one transaction hash are not automatically supported.
API
To generate deposit addresses, check deposit history, and submit Travel Rule originator information programmatically, see Managing Deposits in the API documentation.