What happens when you send BTC from a Taproot address to a swap that only reads legacy

05 September 2026

The swap will likely fail, or your funds may be lost. A swap system that only reads legacy Bitcoin addresses cannot parse or process a transaction sent from a Taproot address.

Here is why.

Bitcoin has gone through several address format upgrades. The earliest was Legacy (starting with "1"), then Pay-to-Script-Hash or P2SH (starting with "3"), then SegWit (starting with "bc1q"), and most recently Taproot (starting with "bc1p"). Each format uses a different script type to lock and unlock coins. A swap service that only indexes legacy addresses is built to watch for transactions that spend from outputs using the older script format. Taproot uses a newer script (called P2TR) that those older parsers simply do not recognize.

When you send BTC from a Taproot address to such a swap, the transaction broadcasts to the Bitcoin network and gets confirmed. The swap's monitoring software, however, scans the blockchain for inputs or outputs matching its expected legacy patterns. It sees a Taproot input. It does not know what to do with it. The swap never registers that you sent funds. It never credits your account. It never triggers the other side of the trade.

In some cases, the swap's software might ignore the transaction entirely. In worse cases, the swap may treat the Taproot input as unspendable or as a noise transaction. If the swap is custodial, your BTC sits in its wallet address, but the system has no record that it belongs to you. Recovering those funds requires contacting support, proving you sent the transaction, and hoping the operator can manually sweep the output. Some operators cannot. Some will not.

Even if the swap uses a refund policy, the refund mechanism itself may only check legacy addresses. You might need to wait for a timeout, then provide a legacy address to get your money back. If you only have a Taproot wallet, you face a second problem: you cannot receive a refund to a Taproot address if the swap's refund system does not support it.

The safe practice is to check what address formats the swap accepts before sending. Most modern swap services list supported address types. If they only say "Legacy" or "BTC (1...)", do not send from a bc1p address. Some swaps now support multiple formats, but many still lag behind Taproot adoption because the upgrade is relatively recent and not all infrastructure has been updated.

This problem is not unique to Taproot. It appears whenever Bitcoin upgrades its address format. The same issue occurred when SegWit addresses first appeared, and some legacy-only systems could not read them. Each upgrade creates a transitional period where older parsers fail on newer transactions.

If you are swapping Bitcoin for another asset, you need to understand that Bitcoin's address system is layered and not backward-compatible in all directions. The hub page "Swapping Bitcoin for other assets" covers the general risks of moving BTC into other chains. This specific case is one of those risks: sending from a format the swap cannot read. Always verify compatibility before you send.

Back to phishing