Skip to content
KeyProof
Home / Guides / WhiteBIT

WhiteBIT: proving you own your self-custody wallet

WhiteBIT uses AOPP (Address Ownership Proof Protocol) so you sign a message in your wallet to prove control of a self-hosted address — no seed phrases, screenshots, or private keys shared. EEA withdrawals also collect wallet type, receiver type and VASP or beneficiary details. Supported verification networks listed include Tron, Solana, BTC, Ethereum, BSC, REEF and Polygon (Voxel).

Never share your seed phrase or private key. WhiteBIT only needs a signature, a small test deposit or the details it asks for in its own app. Last checked 2026-10-27. Not legal advice.
Steps summarise WhiteBIT global help-center articles. WhiteBIT Australia and WhiteBIT Turkey publish separate Travel Rule pages — use the help center for your entity if it differs.
This is your free guide. Free accounts get one exchange guide. Upgrade to Pro for every guide.

When WhiteBIT asks

Where: EEA (Travel Rule / MiCA obligations described for EEA accounts; deposit confirmation also referenced for EU or Turkey in WhiteBIT's Travel Rule withdrawals article). Follow the entity and region shown in your WhiteBIT account.

Threshold: WhiteBIT says Travel Rule API/verification applies when the account is registered in the EEA, the transfer is crypto, regional threshold requirements are met, and Travel Rule features are enabled. Exact numeric thresholds are not published as a single figure in the articles we checked — complete fields when the Verify button or withdrawal form appears.

Accepted verification methods

MethodStatusDetails
AOPP message signatureAcceptedSelect "Received from a self-hosted wallet" on deposit verification (or follow the AOPP UI when offered). Sign the generated message in your wallet and paste/confirm the signature. WhiteBIT documents MetaMask, Ledger, Trezor, Trust Wallet (WalletConnect), BlueWallet (BTC), TronLink (Tron via TronScan), and Phantom/SolScan (Solana). No private keys are exposed.[1][2]
Travel Rule deposit / withdrawal fieldsAcceptedFor VASP-sourced deposits: sender name, residential address fields, and VASP ID or name. For EEA withdrawals: wallet type (hosted/unhosted), receiver type (individual/entity), names, country/address, and VASP info when the destination is hosted.[2]
Satoshi testNot listedNot described in WhiteBIT's AOPP / Travel Rule help articles we checked; ownership proof is via signature.[1][2]
ScreenshotNot listedWhiteBIT highlights AOPP as verification without screenshots or manual data entry for ownership proof.[1]
Signing a message for WhiteBIT? Check the signature before you submit it. Verify it free in your browser and save a proof record. Your keys and seed phrase never leave your wallet.

Unlock the full WhiteBIT guide

You've already used your free guide in this browser. Pro unlocks every exchange guide for $9/mo or $79/yr. Steps stay cited to WhiteBIT's official help pages. We never ask for keys — the free verifier still runs entirely in your browser.

Get Pro — $9/mo Get Pro — $79/yr

Pay with crypto (AnonPay) · See pricing

Step by step

Deposit from a self-hosted wallet (AOPP)[2]

  1. Open History → Deposits, find the deposit that needs Travel Rule data, and press Verify when the button appears.
  2. Select "Received from a self-hosted wallet". WhiteBIT launches an AOPP check.
  3. In your wallet, sign the message shown on the verification interface. Do not share seed phrases or private keys.
  4. Paste the signature into the form (when required) and confirm. Status moves from submitted (awaiting verification) to approved when accepted.
  5. The deposit stays uncredited until Travel Rule steps are completed.

Save the address, message and signature. You can re-check them in the KeyProof verifier. Open the verifier →

Sign by network (examples WhiteBIT documents)[1]

  1. Ethereum / EVM: use Ledger, Trezor, MetaMask, Trust Wallet (WalletConnect) or other listed wallets — connect in AOPP and sign the message.
  2. Bitcoin: BlueWallet — open the wallet → three dots → Sign/Verify Message → paste the AOPP message → sign → paste into WhiteBIT. Ledger is also listed.
  3. Tron: connect TronLink via TronScan → More → Sign & Verify → paste the AOPP message. WhiteBIT notes the Tron signature may need Base64 encoding with a third-party tool before pasting.
  4. Solana: connect via SolScan (or Phantom / MetaMask Solana support) → Sign Message → paste the signature into WhiteBIT (Base64 conversion not required per WhiteBIT's wallet article).
  5. If your network is not in WhiteBIT's supported verification list, WhiteBIT says to select withdrawal to another exchange and enter the wallet name in the VASP field, or follow the on-screen alternative.

EEA crypto withdrawals — Travel Rule fields[2]

  1. Start a crypto withdrawal.
  2. Set Wallet Type: VASP-hosted (hosted) or self-custody (unhosted).
  3. Set Receiver Type: Individual (first name, last name, country of residence, address) or Legal Entity (full name, country, address).
  4. If hosted, pick the VASP ID from WhiteBIT's list or enter the VASP name. For unhosted destinations, VASP information is not required.
  5. Submit. Incomplete mandatory fields can delay or reject the request.

Common errors and fixes

Deposit not credited after sending

Complete History → Deposits → Verify. Self-hosted deposits need a successful AOPP signature; VASP deposits need matching sender name/country and VASP details. Status stays submitted until approved.[2]

Tron or Solana signature rejected

WhiteBIT documents manual Sign & Verify flows on TronScan/SolScan. For Tron, convert the signature to Base64 if required before pasting. WhiteBIT notes it is not responsible for failures that depend on third-party wallets/services.[1][2]

Verified on one network, asked again on another

WhiteBIT says you must verify again per network (for example Polygon vs Ethereum).[2]

Network not supported for Web3 verification

WhiteBIT lists supported networks (Tron, Solana, BTC, Ethereum, BSC, REEF, Polygon/Voxel). For others, use the VASP/wallet-name path described in help, or contact official support.[1][2]

FAQ

Does AOPP expose my private key?

No. WhiteBIT describes AOPP as proving control by signing a message without revealing sensitive data or private keys.

Do these Travel Rule fields apply worldwide?

WhiteBIT's FAQ in the withdrawals article says the updates currently apply specifically to users from the EEA region for those changes. Deposit confirmation text also references EU or Turkey for certain cases. Follow your account's region.

Are fiat transfers affected?

WhiteBIT says these Travel Rule changes apply to crypto deposits and withdrawals; fiat is unaffected.

Sources

Last checked 2026-10-27. Numbers in brackets [n] in the text refer to this list.

  1. Verifying Your Non-Custodial Wallet in Line with the Travel Rule (WhiteBIT Help) (official)
  2. Travel Rule Requirements: Updates to Crypto Withdrawals Interface and API (WhiteBIT Help) (official)

KeyProof is not affiliated with WhiteBIT. This guide summarizes WhiteBIT's public help pages and may be out of date. Always follow the instructions in your WhiteBIT app. Not legal, tax or financial advice.