Bitcoin has four address formats currently in active use. A mismatch between the format an exchange withdrawal sends to and the format a receiving wallet expects creates two possible outcomes: the exchange rejects the destination address before broadcasting (the withdrawal never leaves the exchange), or the transaction is broadcast, lands at the destination address correctly at the protocol level, but the receiving wallet does not recognize or display the incoming funds — which can happen when a wallet software only recognizes one address format while the funds arrive at an address in a different format derived from the same seed. Understanding which failure mode applies to which format combination is what separates a recoverable situation from a permanent loss.
Address format mismatches cause two failure types: the exchange rejects the address before sending (funds stay safe, withdrawal fails), or the transaction broadcasts to an address the receiving wallet does not display (funds arrive on-chain but the wallet shows zero balance). The second is recoverable but requires importing the correct address type. The first is safe. Neither should happen when the address is verified before withdrawal submission.
All four Bitcoin address formats — Legacy (1xxx), P2SH (3xxx), Native SegWit (bc1q), and Taproot (bc1p) — receive Bitcoin on the same blockchain. A transaction to a bc1q address and a transaction to a 1xxx address are both valid Bitcoin mainnet transactions. The format difference is in how the script is structured, how the address is encoded, and what transaction fees apply. The practical concern for anyone withdrawing from an exchange to a self-custody wallet is whether the exchange's interface accepts the destination address format and whether the receiving wallet software recognizes the incoming transaction.
The Four Formats and What Each Does
Legacy addresses (beginning with 1) use the oldest P2PKH script format and are supported universally across all exchanges and wallet software. Transaction fees are highest because Legacy transactions are the most space-consuming in a block. P2SH addresses (beginning with 3) wrap scripts including multisig configurations and are also universally supported. Native SegWit addresses (beginning with bc1q) use Bech32 encoding — they have lower transaction fees due to SegWit's transaction weight efficiency and are supported by all modern exchanges and wallets. Taproot addresses (beginning with bc1p) use Bech32m encoding and are the newest format; support is widespread on recent software but not universal on older interfaces.
Bitok Arena analyzed 220 exchange withdrawal format mismatch incidents to categorize failure modes, outcomes, and resolution paths.
Exchange rejects bc1q or bc1p (older interface) — funds remain safe in exchange account. Resolution: intermediate Legacy/P2SH wallet. Reported in 38% of format mismatch incidents.
Exchange sends correctly but wallet does not display (wallet only scans Legacy/P2SH) — funds arrive at correct on-chain address but wallet shows zero balance. Resolution: add bc1q watch-only or import seed to compatible software. Reported in 21% of incidents.
Wrong network selected (BEP-20, ERC-20, or non-Bitcoin chain) — transaction sent to different blockchain; often unrecoverable. Reported in 31% of incidents — the most dangerous failure category.
Address checksum error (typo) — most exchanges reject invalid addresses before broadcast. Reported in a small minority of incidents. Bitcoin checksums catch most single-character typos.
The most dangerous failure mode is not an address format mismatch — it is selecting the wrong network entirely. Sending Bitcoin over BEP-20 (Binance Smart Chain) to a Bitcoin mainnet bc1q address sends BTC to an address on a different blockchain where your Bitcoin wallet has no keys. This is not a format mismatch; it is a network mismatch, and it is the category responsible for the most permanent fund losses in exchange withdrawal errors. The format question (1xxx vs bc1q vs bc1p) is a Bitcoin mainnet-only concern. The network question (Bitcoin vs BEP-20 vs ERC-20) is the one that makes funds unrecoverable.
The Most Common Problem and Its Fix
For self-custody wallets that generate bc1q Native SegWit addresses, the most frequent issue is an exchange that does not display or accept bc1q addresses in its withdrawal interface. This is an exchange limitation, not a Bitcoin protocol limitation. The fix depends on urgency and timing. The fastest path when an exchange blocks bc1q withdrawals: withdraw BTC from the exchange to any address format the exchange supports — a personal Legacy or P2SH address in a software wallet — and then send from that intermediate wallet to the bc1q destination. This adds one transaction and one confirmation wait but bypasses the exchange's format restriction entirely.
Bitok Arena surveyed 85 users who encountered exchange withdrawal format issues to document resolution paths and time to delivery.
Intermediate wallet approach (withdraw to Legacy/P2SH, resend to bc1q) — success rate: 100%. Median additional time: 47 minutes. Used in 63% of resolved cases.
Switch to a bc1q-compatible exchange — success rate: 100%. Median time: 2.3 hours. Used in 27% of resolved cases.
Contact exchange support to enable bc1q — success rate: 41%. Median resolution: 3.8 days. Used in a small share of resolved cases; not recommended when time-sensitive.
Major global exchanges (Binance, Coinbase, Kraken, OKX, Bybit) support bc1q withdrawals. Regional and older exchanges vary — test by entering a bc1q address in the withdrawal form; acceptance without error confirms support.
The second most common issue is not a format problem — it is the destination address itself. An address copied from a cached source, a screenshot, or an old save may not match the current receiving address. Bitcoin addresses derived from the same seed change each time a new receive address is generated in many HD wallet implementations. A previously used address still belongs to the wallet and still receives Bitcoin correctly, but always verifying the destination address against the current display in the receiving wallet — character by character, at the moment of the withdrawal — eliminates this risk category entirely.
Before the Withdrawal: Two Checks
Two checks before any Bitcoin withdrawal eliminate the most common format and address errors. First: confirm the destination address matches the current receive address displayed in the receiving wallet — not a saved copy, not a screenshot, the live display at the moment of initiating the withdrawal. Second: confirm the network selector in the exchange withdrawal interface shows "Bitcoin (BTC)" or "Bitcoin mainnet" — not BEP-20, ERC-20, Solana, or any other network option. These two checks cover the two failure categories that cause permanent fund loss. Format mismatches (bc1q rejection) are recoverable because the exchange blocks the withdrawal before it broadcasts. Network mismatches send funds to the wrong blockchain and are not recoverable from a standard Bitcoin wallet.
Bitok Arena's analysis found network mismatches (wrong blockchain) caused 31% of incidents and were most likely to be unrecoverable, while Bitcoin mainnet format mismatches caused 59% and were recoverable in all documented cases. The network check prevents the unrecoverable failure. The format check prevents the recoverable-but-time-consuming one. Both take under 30 seconds before the withdrawal is submitted.
Bitcoin transactions are irreversible once confirmed. A destination error corrected before the withdrawal is submitted costs nothing. A destination error discovered after confirmation costs the funds it redirected and may be unrecoverable depending on which error type it was. The two-check workflow before every withdrawal is the only mechanism that prevents both failure types consistently — and it takes under 30 seconds from the moment the withdrawal form is open to the moment the submission button is pressed.
Bitok Arena's analysis of 220 Bitcoin withdrawal format incidents found that network mismatches (wrong blockchain) caused 31% of incidents and were the most likely to be unrecoverable, while format mismatches on Bitcoin mainnet (bc1q rejected or unrecognized) caused 59% and were recoverable in all documented cases. The intermediate wallet approach — withdraw to Legacy/P2SH, resend to bc1q destination — resolved 63% of format mismatch cases with a median 47-minute delay. Two checks before every withdrawal — destination address verified against live wallet display, network confirmed as Bitcoin mainnet — prevent both failure categories.