Binance Withdrawal Whitelist and Address Book Setup

How to enable the Binance withdrawal whitelist, understand the 24-hour cooldown on new addresses, name entries consistently, and set up separate whitelists for main and sub-accounts.

Published on 2026-07-12 · About 25 min read · Security Settings

The Biabahub desk reviewed twelve withdrawal incidents in May 2026. Seven of them could have been prevented simply by having the withdrawal whitelist on. This post shares the internal playbook we now use across the team to weld the last door out of Binance a little more tightly. When you need to log back in and check your configuration, go through Binance Official Site; on mobile, keep the app up to date via Download Binance App, or open /en/download/ for other platforms.

Short Answer: When Must the Withdrawal Whitelist Be Enabled?

As soon as the account holds more than about 1,000 USDT of net value, or you have ever connected to third-party DApps, cross-chain bridges, or small bots, the whitelist has to be on. With the whitelist enabled, any withdrawal to an address that is not on the list is refused outright — even an attacker with your password and 2FA cannot exfiltrate the funds to an unknown wallet. Setup takes about eight minutes. The path is fixed at Account, Security, Withdrawal Address Whitelist. Once switched on, each new address goes through a 24-hour cooldown before it can be used.


1. Path and Switch: Turning the Whitelist On

Start on the web, where the fields are laid out cleanly, and use the app for later day-to-day edits.

1.1 Web setup path

  1. Sign in, click the avatar, choose Account, then Security in the left menu.
  2. Locate Withdrawal Address Whitelist and flip the slider from grey to blue On.
  3. The system prompts for email verification and 2FA. Complete both.
  4. The page shows a red banner at the top: "Whitelist enabled. Only listed addresses may withdraw."
  5. If the list is empty, every withdrawal will be blocked. That is expected.

1.2 App setup path

  • Open the app, tap Wallet at the bottom, then the three-dot menu in the top-right, then Settings.
  • Choose Security, Address Management, Whitelist Switch.
  • The confirmation flow mirrors the web: 2FA plus email code.
  • After the first activation, sign out and back in to make sure the state has synchronized across devices.

1.3 Switch states at a glance

State Usable addresses Immediate use Best for
Whitelist Off Any address Instant Frequent small withdrawals to different wallets
Whitelist On Only listed 24-hour cooldown Long-term holdings, main account
Whitelist On + hardened Only listed, extra confirm every time Cooldown plus per-withdrawal 2FA Balances above 50,000 USD

Our team runs main accounts in the "On plus hardened" mode. Trading tempo drops, but security margin rises with it.


2. New Addresses and the 24-Hour Cooldown

The cooldown is the whitelist's central defensive mechanism. Understand it and you use the feature properly.

2.1 How the countdown works

  • Start point — the second the new address is submitted and 2FA succeeds.
  • Length — exactly 24 hours, unaffected by time zones or day changes.
  • Visualization — the row shows a grey "Cooling" tag and the remaining hours.
  • Early use — not supported. Support tickets asking for a shortcut are rejected by policy.
  • Delete and re-add — triggers a fresh 24-hour cooldown; you cannot bypass by cycling.

Q: Can I edit the address while it is cooling down? A: No, but you can delete it. Deletion is immediate and leaves no cooldown residue. Editing effectively means "delete, re-add, wait another 24 hours." One incident we handled involved an EOS address whose memo was short by one digit — funds sat on-chain for 27 hours from discovery through re-cooldown, during which the price moved 6.2 percent. Character-by-character verification on new addresses is not optional. Copy, paste, compare the first four and last four characters, then compare the memo.

2.2 The five-step address-add checklist

  1. Copy the target address to the clipboard, straight from the recipient's official page — not from chat logs or screenshots.
  2. Paste into the Binance address book field but do not confirm yet.
  3. Read aloud the first four characters and the last four, checking both ends.
  4. On XRP, EOS, BNB Beacon, TON, and similar chains, also confirm the memo or tag.
  5. Confirm, enter 2FA and email code, and the entry enters cooldown.

The team rule: any address addition needs two people. One types, one reads back, then both sign off.


3. Naming Conventions for the Address Book

Labels are for your future self. "Wallet 1" is useless in six months. Here is the schema we have used for two years.

3.1 Template

purpose-asset-chain-year[-notes]

Purpose keyword Meaning Example
coldwallet Hardware cold wallet coldwallet-btc-2026
hotwallet Hot / desktop wallet hotwallet-usdt-trc20-2026
exchange Another exchange exchange-okx-eth-2026
defi DeFi contract defi-aave-usdc-2026
paycheck Salary or settlement paycheck-usdt-erc20-2026-Q3
ops Team ops address ops-bnb-bsc-2026-marketing

3.2 Anti-patterns

Bad label Problem Fix
wallet1 No information coldwallet-btc-2026
My address Native language plus no purpose hotwallet-eth-2026
test Blurs into production test-usdt-trc20-donotuse
Binance to OKX Both sides unclear exchange-okx-eth-2026
ledger Vendor without chain coldwallet-btc-2026-ledger

3.3 Payoff of good naming

  • Second-check on withdrawal — the dropdown groups by purpose, so misclicks drop.
  • Audit-ready — the annual audit can read the labels alone to trace flows.
  • Multi-asset grouping — a fuzzy search for coldwallet- returns every cold wallet.

4. Minimum Withdrawal and Fee Reference for Top-10 Assets

Values snapshotted on July 1, 2026 from Binance's public schedule. Binance adjusts fees periodically, so always confirm inside the app.

Asset Network Minimum Fee Whitelist needed Notes
BTC BTC 0.0005 0.0002 Yes Prefer Lightning for large amounts
ETH ERC20 0.005 0.0012 Yes Gas is volatile
USDT TRC20 10 1 USDT Yes First choice for small-to-mid amounts
USDT ERC20 50 3.4 USDT Yes Stable for large amounts
USDT BEP20 5 0.29 USDT Yes Inside the BSC ecosystem
USDC ERC20 30 3.2 USDC Yes Regulatory friendly
BNB BEP20 0.02 0.0005 Yes Launchpad participation
SOL SOL 0.05 0.005 Yes Fast on-chain finality
XRP XRP 22 0.25 Yes plus memo Missing memo strands funds
TRX TRX 10 1 Yes Frequently used for gas top-up

Red flag: "zero-fee withdrawals" or "discounted withdrawals" from third parties are never official. Ignore.


5. Do Sub-Accounts Share the Whitelist?

This is one of the most common questions in the support tickets.

5.1 Sharing rules

  • The main-account whitelist does not automatically extend to sub-accounts. Each sub-account must be configured independently.
  • Sub-account address books are visible to the main account to simplify audit.
  • The main account can gate withdrawals with a master switch — even a fully whitelisted sub-account cannot ship funds if the master toggle is off.
  • Sub-account API keys can only withdraw to that sub-account's own whitelist; they cannot borrow the main account's list.

5.2 Recommended enterprise topology

  1. Main account — keeps two or three cold wallets, no day-to-day withdrawals.
  2. Trading sub-account A — only internal transfer addresses on its whitelist.
  3. Operations sub-account B — only known payment processor addresses.
  4. Emergency sub-account C — whitelist empty, used only for internal rebalancing.
  5. Weekly review through the main account of the sub-account whitelist change log.

Related reading:


6. When the Address Book Is Tampered With via XSS

A widely reported case in November 2025 involved a malicious browser extension that tampered with both the clipboard and the DOM of the exchange page. The chain looked like: hostile extension, clipboard interception, DOM substitution of the displayed address, and finally the user pastes what looks like their own recipient but is actually the attacker.

  • Trigger — an over-privileged browser extension with "read all website data."
  • Countermeasure — Binance renders the address on the final withdrawal confirmation as an image with the first six and last six characters — verify against the image with your eyes, not by copying text.
  • Biabahub practice — in the browser you use for Binance, keep only essential extensions (password manager plus uBlock); move everything else to a separate browser profile.
  • Extra layer — enable the "video confirmation for high-value withdrawals" feature so that any withdrawal above 10,000 USDT triggers a liveness check.

Frequently Asked Questions

Q1: The whitelist is on but I urgently need to send funds to a new address. What do I do?

Add the address and let the 24-hour cooldown run. In the meantime, move the funds via internal transfer, P2P, or spot trading into an account whose whitelist already contains the destination, and withdraw from there. Do not turn the whitelist off to save time — turning it off also requires a 24-hour cooldown to take effect, so you lose safety without gaining speed.

Q2: How many addresses can I whitelist?

The per-account cap is around 200. We have never come close to it in practice. We do recommend fewer than 20 on a main account — beyond that the "whitelist" is no longer meaningfully restrictive.

Q3: Does deleting a whitelist entry take effect immediately?

Yes. Deletion is instant, no cooldown. That asymmetry is intentional: deletion is immediate, addition is delayed, biased toward preventing unauthorized outflow.

Q4: Does changing my phone number affect the whitelist?

No. The whitelist is bound to the account UID, not the phone number. Changing the phone number may however trigger Binance's account security review, which typically restricts withdrawals for 24 to 72 hours.

Q5: Can I distinguish multiple addresses for the same counterparty via notes?

Yes. Binance allows same-name entries with different addresses. Our naming convention appends -01 / -02 or the chain name — for example exchange-okx-usdt-trc20-2026 and exchange-okx-usdt-erc20-2026.

Q6: Can whitelist addresses leak from Binance itself?

No such public disclosure is on record. Technically the whitelist only renders after login plus 2FA, and server-side storage should be encrypted. Do not treat "cannot leak" as gospel, though — for cold-wallet main addresses, consider using on-chain privacy techniques such as stealth addresses to reduce exposure at the source.

Q7: Can the whitelist be turned off entirely?

Yes, but disabling also carries a 24-hour cooldown. The whitelist remains enforced during the cooldown, and if a hostile login appears during that window you still have 24 hours to re-enable and lock the account down.


Risk Notice

This post is technical education for whitelist and address book configuration. It is not investment advice, not legal advice, and not a promise about any specific address book state. Crypto withdrawals are irreversible: once funds go to the wrong destination — typo, missing memo, wrong chain — recovery is essentially impossible, and every operation is on the user. The whitelist significantly reduces theft risk, but does not defend against the account owner personally being socially engineered into adding a hostile address — the cooldown only delays; after 24 hours the attacker can still withdraw. Combine the whitelist with 2FA, backup codes, an anti-phishing code, and email notifications to build a layered defense. Avoid putting real amounts, real coin counts, or real identity details into your address book labels so that a lost device does not become a treasure map. Anyone asking you to "send the whitelist to support so we can help configure it" is running a scam; Binance never asks for address book contents. To reach the real login, use Binance Official Site; for the app, use Download Binance App.

Published 2026-07-01. Next revision planned 2026-10-01.