存款

  • 更新

创建存款地址

可以在每种资产的存款页面上创建存款地址。可以从主页访问每种资产的存款页面 钱包页面,可以通过单击 Deribit 用户界面中的钱包图标来访问该图标。

要进入资产的存款页面,请点击相关资产旁边的存款按钮。

进入存款页面后,点击 “生成存款地址” 按钮即可生成存款地址。

可以在主账户和所有子账户上创建存款地址。每个子账户都有自己的存款地址,存入子账户存款地址的任何存款都将直接存入该子账户

重要

[en] For custody-enabled clients, the deposit process is different. Please contact custody@deribit.com for guidance. You can also review our Custody Options article.

注意

账户必须已在上完成验证流程 验证页面 在生成存款地址之前。

注意

对于比特币,每24小时可以生成一个新地址。

对于 ERC20、Solana 和 XRP,只能生成一个地址。

注意

如果生成了 ERC20 地址,则将为使用 ERC20 地址的每项资产自动添加该地址。

查找您的存款地址,进行存款

存款地址可以在每种资产的存款页面上找到。可以从主页访问每种资产的存款页面 钱包页面,可以通过单击 Deribit 用户界面中的钱包图标来访问该图标。

要进入资产的存款页面,请点击相关资产旁边的存款按钮。

警告

确保您仅使用支持的协议进行存款。在不正确的协议或链上存入的任何存款都可能无法收回

应特别注意使用哪种货币和网络。并非所有资产都支持所有网络。详细信息将在每种资产的存款页面上提及。

重要

[en] 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.

支持的协议和确认

存款和取款要求和限制:

除非另有说明,否则请勿使用任何打包的代币或替代链/协议。Deribit 可能无法收回通过相关特定资产存款页面上未特别提及的方法发送的资金

存款记录

在存款历史记录中,将显示所有存款。此表按资产列报。

字段

描述

地址

存款到的 Deribit 地址

金额

相关资产中的金额

上次更新

上次更新存款的日期和时间

状态

要么待处理(等待 Deribit 的确认或批准)要么已完成

税务信息

存款的交易哈希

注意

用于向存款添加个人备注的字段

存款未入账

存款可能尚未存入账户的原因有几个。

  • 确保存款是在支持的协议上完成的。

  • 确保在区块链上确认存款并进行足够的确认。

  • 存款将在达到要求的确认后的几分钟内记入账户。

  • 收到存款的账户必须已完成验证流程 验证页面 在主账户中。

  • 不自动支持在一个交易哈希中向同一个地址进行多次存款。

[en] Managing Deposits in API

[en] This section explains how to generate deposit addresses, check deposit history and submit originator information for the Travel Rule using API. Before calling any private method you must authenticate.

提示

[en] Please refer to API 身份验证指南 for more information regarding authenication.

[en] Creating a deposit address

[en] In order to generate a new on-chain deposit address for a selected currency use the private/create_deposit_address method. Each subaccount has its own deposit address. Only verified accounts can generate addresses.

[en] Example Request: 

{
  "jsonrpc": "2.0",
  "id": 7538,
  "method": "private/create_deposit_address",
  "params": {
      "currency": "BTC"
  }
}

[en] Response: On success the API returns an object with:

  • [en] address – New deposit address on the blockchain

  • [en] creation_timestamp – UNIX millisecond timestamp when the address was created

  • [en] currency – Asset for which the address was created

  • [en] type – Always deposit

{
    "jsonrpc": "2.0",
    "id": 7538,
    "result": {
        "address": "2N8udZGBc1hLRCFsU9kGwMPpmYUwMFTuCwB",
        "creation_timestamp": 1550575165170,
        "currency": "BTC",
        "type": "deposit"
    }
}

[en] If you already generated an address and only want to retrieve it, use /private/get_current_deposit_address with the same currency parameter. This returns the existing address and its status.

[en] Retrieving deposit history

[en] In order to obtain a list of completed or pending deposits for a selected currency, use the private/get_deposits method. This method returns information about past deposits, including the deposit address, credited amount, last update time, current status (pending or completed), and the blockchain transaction hash. The API provides the same details that are visible in the web deposit history.

[en] Example Request: 

{
  "jsonrpc": "2.0",
  "id": 5611,
  "method": "private/get_deposits",
  "params": {
      "currency": "BTC",
      "count": 10,
      "offset": 0
  }
}

[en] Response: The result has the fields count and data. Each entry in data includes:

  • [en] address – Deposit address on Deribit

  • [en] amount – Amount credited in the relevant currency

  • [en] clearance_state - Clearance state indicating the current status of the transaction clearance process. Allowed values:

    • [en] in_progress: clearance process is in progress

    • [en] pending_admin_decision: transaction is under manual review by Deribit admin

    • [en] pending_user_input: user should provide additional information regarding the transaction

    • [en] success: clearance process completed successfully

    • [en] failed: clearance process failed, transaction is rejected

    • [en] cancelled: transaction is cancelled (currently used only for withdrawals, meaning the withdrawal is cancelled)

    • [en] refund_initiated: clearance process failed, transaction refund is initiated, funds are removed from Deribit balance (valid for deposits only)

    • [en] refunded: clearance process failed, deposit amount is refunded back to the client (valid for deposits only)

  • [en] currency – Name of the currency

  • [en] note (optional) - Optional note added by the user to the deposit on web-page.

  • [en] received_timestamp – When the deposit transaction was first seen on-chain

  • [en] refund_transaction_id - Blockchain transaction hash if refunded

  • [en] source_address - Originator address

  • [en] state – Deposit state. Possible states:

    • [en] pending: deposit detected on blockchain/system, compliance not yet finished

    • [en] completed: compliance check finished successfully

    • [en] rejected: deposit failed compliance and must be handled manually

    • [en] replaced: deposit transaction was replaced on the blockchain and should have a new transaction hash

  • [en] transaction_id – Blockchain transaction hash

  • [en] updated_timestamp – Last update time (used when status changes)

{
  "jsonrpc": "2.0",
  "id": 5611,
  "result": {
        "count": 1,
        "data": [
          {
              "address": "2N35qDKDY22zmJq9eSyiAerMD4enJ1xx6ax",
              "amount": 5,
              "currency": "BTC",
              "received_timestamp": 1549295017670,
              "state": "completed",
              "transaction_id": "230669110fdaf0a0dbcdc079b6b8b43d5af29cc73683835b9bc6b3406c065fda",
              "updated_timestamp": 1549295130159
          }
      ]
  }
}

[en] If you receive an empty list, the deposit may not have enough confirmations. Deposits on Deribit are credited a few minutes after the required number of confirmations. Ensure that you are using the correct protocol and network and that the account is verified.

[en] Submitting originator information

[en] For deposits exceeding AED 3 500 (about USD 953), Deribit must collect and exchange originator data with the sending VASP. If the required information is not received, the deposit will still be credited. However, those funds will be locked and cannot be used for any activity, including withdrawals, transfers, opening new positions, or spot trading, until the originator details are supplied.

[en] In order to provide the originator’s details for deposits that require Travel Rule compliance, you can either:

[en] In the web interface, deposits arriving from a new blockchain address are marked with a Missing Info label, prompting you to submit the originator’s information.

[en] Information to provide:

  • [en] Type of wallet: use the personal parameter to confirm whether the deposit comes from your own unhosted wallet (e.g. Ledger, MetaMask). If the wallet is hosted by another exchange, you will need to provide the counterparty VASP details.

  • [en] Originator confirmation: if you are not the originator, include the beneficiary_first_name and beneficiary_last_name (or beneficiary_company_name if applicable), together with the beneficiary_address.

  • [en] Counterparty VASP: for hosted wallets, provide the VASP’s details, including beneficiary_vasp_name, beneficiary_vasp_did, and, if required, the beneficiary_vasp_website.

  • [en] Consent: use the agreed parameter to confirm that you allow Deribit to share the provided information with third parties as part of Travel Rule compliance.

[en] Example Request: 

{
  "jsonrpc": "2.0",
  "method": "private/add_to_address_book",
  "id": 42,
  "params": {
    "currency": "BTC",
    "type": "deposit_source",
    "address": "bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf0uyj",
    "label": "Main address",
    "beneficiary_vasp_name": "Money`s Gone",
    "beneficiary_vasp_did": "did:example:123456789abcdefghi",
    "beneficiary_first_name": "John",
    "beneficiary_last_name": "Doe",
    "beneficiary_address": "NL, Amsterdam, Street, 1",
    "agreed": true,
    "personal": false
  }
}

[en] Response: 

{
  "jsonrpc": "2.0",
  "id": 42,
  "result": {
    "address": "bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf0uyj",
    "creation_timestamp": 1536569522277,
    "currency": "BTC",
    "type": "deposit_source",
    "label": "Money's Gone wallet",
    "beneficiary_vasp_name": "Money`s Gone",
    "beneficiary_vasp_did": "did:example:123456789abcdefghi",
    "beneficiary_first_name": "John",
    "beneficiary_last_name": "Doe",
    "beneficiary_address": "NL, Amsterdam, Street, 1",
    "agreed": true,
    "personal": false,
    "info_required": false
  }
}

[en] Notes and best practices

  • [en] Supported protocols and confirmations: Check the supported networks and the number of confirmations required for each asset on the deposit page.

  • [en] Always use correct chains: Depositing via unsupported chains or wrapped tokens may result in unrecoverable funds.

  • [en] Verification required: You must complete account verification before you can generate deposit addresses.

  • [en] Multiple deposits in one transaction: Sending multiple deposits in a single transaction may delay crediting.

  • [en] Travel Rule compliance: Provide accurate originator details when prompted. Incomplete or incorrect information can lead to withdrawal locks.