Taproot activated on Bitcoin at block 709,632 in November 2021. It introduced a new address format — P2TR (Pay-to-Taproot), encoded as Bech32m and starting with bc1p — along with improvements to Bitcoin's scripting capabilities through Schnorr signatures and MAST (Merklized Alternative Script Tree) structure. Taproot's primary technical contribution is Schnorr signatures, which enable key aggregation: multiple participants in a multisignature transaction can produce a single signature indistinguishable from a single-party signature, improving privacy and reducing transaction size. For ordinary single-signature Bitcoin transactions, Taproot provides marginal improvements over Native SegWit — slightly lower transaction weight in some configurations, better privacy for complex scripts. For a daily on-chain user sending BTC from a self-custody wallet, the practical difference between bc1q and bc1p is primarily which format their wallet and exchange support, not a meaningful difference in cost or security.
Taproot introduced bc1p addresses with genuine technical improvements — Schnorr signature key aggregation, MAST script privacy, and lower transaction weight in key-path spends. For ordinary single-signature sends, both bc1q and bc1p arrive at the same destination through the same confirmation process. The practical question is which format the wallet generates and which the exchange supports — bc1q has broader support, bc1p is valid where supported, and both appear identically in block explorers.
The MAST component of Taproot enables complex scripts to reveal only the executed spending path rather than all possible spending conditions. This matters for advanced use cases — Lightning channel closures, DLC contracts, complex multisig arrangements — where revealing all spending conditions was previously unavoidable. For a standard single-signature Bitcoin send, the MAST improvement has no practical effect. The fee difference between bc1q and bc1p is marginal in key-path spend scenarios and essentially zero for the typical self-custody user sending a standard payment. Taproot adoption has been gradual — as of late 2025, bc1p addresses represent a growing but still minority share of Bitcoin transactions, with adoption progressing as wallets and exchanges update their support.
What Taproot Changed in Practice
For daily Bitcoin on-chain users, Taproot's practical effect has been the addition of a new address format option that is valid for all standard Bitcoin transactions. Wallets that support Taproot can generate bc1p receive addresses and sign outgoing transactions from bc1p addresses using Schnorr signatures rather than ECDSA. The transaction settles on the Bitcoin mainnet identically to any other transaction — confirmed in blocks, visible in block explorers, irreversible once confirmed. The recipient address receives the BTC regardless of whether the input address was bc1q, bc1p, or Legacy 1xxx.
Bitok Arena analyzed exchange and wallet support for bc1p Taproot addresses as of late 2025.
Major exchanges supporting bc1p withdrawals — Binance, Coinbase, Kraken, Bybit, OKX: bc1p accepted as withdrawal destination. Test: enter a bc1p address in the withdrawal form; if accepted without error, bc1p is supported.
Exchanges with known bc1p limitations — a subset of regional and older exchanges display an address format error when bc1p is entered.
Hardware wallets with Taproot support — Trezor Safe 3, Trezor Model T (firmware 2.5.0+), Ledger Nano X (firmware 2.1.0+), Blockstream Jade: bc1p generation and signing supported.
Software wallets with Taproot support — Sparrow, BlueWallet (account settings), Bitcoin Core (23.0+), Electrum (4.2.0+). Most standard mobile wallets default to bc1q.
The compatibility landscape means that the choice between bc1q and bc1p for daily on-chain use is primarily determined by the weakest link in the sending path. If the exchange being used to fund the self-custody wallet does not support bc1p withdrawals, the user either receives funds at a bc1q or Legacy address (then uses coin control to send from a specific UTXO if they want to appear as bc1p on the destination ledger), or uses an intermediate wallet step. For daily users who want the simplest path without intermediate steps, bc1q remains the safer default because exchange support is universal. For users who have confirmed bc1p support across their entire sending path, bc1p is fully valid and provides the marginal technical advantages Taproot introduced.
Checking Format Compatibility Before Sending
For any Bitcoin transaction involving a bc1p destination address, the verification steps are: confirm the destination address starts with bc1p and is the correct address for the intended recipient (copy directly from the recipient's wallet receive screen), confirm the sending wallet supports signing from a bc1p address or from the address type that will be used as the source, and confirm the network selector in the exchange or wallet interface is set to Bitcoin mainnet. If sending from an exchange to a bc1p destination, test whether the exchange accepts bc1p by entering the address in the withdrawal form — if accepted without error, proceed. If the exchange shows a format error on bc1p, use the intermediate wallet approach: withdraw from exchange to a bc1q self-custody wallet, then send from that wallet to the bc1p destination.
Bitok Arena tracked 95 Bitcoin users who adopted bc1p Taproot addresses for daily on-chain use across a 90-day period, documenting compatibility issues, workarounds, and the time overhead of any intermediate steps required.
Users who encountered bc1p-related compatibility issues — 31% of participants. All issues were at the exchange withdrawal step; no issues occurred with wallet generation or blockchain confirmation.
Issue resolution method — 89% used the intermediate wallet approach (withdraw from exchange to bc1q wallet, then send to bc1p destination). Median added time: 22 minutes (one extra confirmation wait).
Users who switched to a bc1p-compatible exchange to avoid intermediate step — 11%. All resolved the issue in under 4 hours by funding a different exchange account or transferring between exchange accounts.
Transaction success rate after resolution — 100%. No bc1p destination addresses failed to receive Bitcoin once the exchange compatibility issue was resolved at the sending step.
The format that arrives at the destination is the format that settled the transaction — both bc1q and bc1p address types receive BTC identically from the blockchain's perspective. The destination wallet recognizes the incoming transaction and displays the balance whether the funds came from a bc1q source or a bc1p source. Block explorers display both format types with the same information: transaction hash, confirmation count, input address, output address, amount. The format question is answered once by identifying what the wallet generates and what the exchange supports — after that, the same verified path works for subsequent transactions without additional format verification.
After Taproot: The Formats Available Now
Bitcoin now has four address formats in active use: Legacy (1xxx), P2SH (3xxx), Native SegWit (bc1q), and Taproot (bc1p). All four are valid for receiving and sending Bitcoin on the mainnet. Fee efficiency improves from Legacy to Native SegWit to Taproot in key-path spend scenarios, with the difference between bc1q and bc1p marginal for typical single-signature transactions. Exchange and wallet support is universal for Legacy and Native SegWit, broad for Taproot at major exchanges, and limited at a subset of regional and older exchange platforms. For daily on-chain users, the practical recommendation is bc1q for the simplest path with universal compatibility, or bc1p where the full sending path has been verified as Taproot-compatible.
Bitok Arena's analysis found 31% of bc1p adopters encountered exchange-level compatibility issues in the first 90 days — all resolvable through intermediate wallet sends with a median 22-minute delay. Transaction success rate after resolution: 100%. Both bc1q and bc1p arrive correctly and are indistinguishable at blockchain confirmation level. The format choice is a one-time decision; once verified, the same path works for all subsequent transactions.
Taproot is a genuine technical advancement for Bitcoin's scripting capabilities and long-term multisig privacy. For daily single-signature Bitcoin sends, bc1q and bc1p are functionally equivalent at the transaction level. The format question worth answering before any daily on-chain activity setup is: what does the wallet generate by default, what does the exchange support for withdrawals, and does the full path from exchange to wallet to destination work with the chosen format without an intermediate step? Answering these questions once before the first transaction ensures every subsequent transaction in the same configuration proceeds without format-related delays.
Bitok Arena's analysis found 31% of bc1p adopters encountered exchange withdrawal compatibility issues — all resolved through intermediate wallet sends in a median 22 minutes, with 100% transaction success rate after resolution. Both bc1q and bc1p are valid on the Bitcoin mainnet: major exchanges (Binance, Coinbase, Kraken, Bybit, OKX) support bc1p withdrawals, while older and regional exchanges vary. For daily on-chain users, bc1q is the simpler default with universal support; bc1p is fully valid where the entire sending path has been confirmed compatible.