Which Bitcoin address type should you use to avoid a failed swap deposit

05 September 2026

Use a native SegWit (bech32) address starting with "bc1q" for Bitcoin deposits into a swap. This address type avoids the most common failure modes - incorrect formatting, mismatched transaction sizes, and rejected deposits - that plague older address formats when moving Bitcoin to other chains.

Why address type matters for swaps

A swap deposit is not a simple peer-to-peer transfer. The exchanger must parse your incoming transaction, match it to your order, and forward the swapped asset. Any ambiguity in the address format can break this chain. Bitcoin supports three major address types, and each behaves differently when the exchanger's software tries to read it.

Legacy addresses (P2PKH) start with "1". They are the oldest format, widely supported, but carry a higher transaction fee per byte because the script is larger. More critically, some modern swap systems treat legacy addresses as a fallback option - and fallbacks sometimes fail silently. A deposit to a legacy address may be accepted by the network but not recognized by the exchanger's automated monitoring.

Pay-to-Script-Hash (P2SH) addresses start with "3". These are often used for multisig or compatibility layers. For a simple swap deposit, they introduce unnecessary complexity. The exchanger's system must decode the script hash, verify it matches a known template, and then extract the public key. Any deviation - even a valid but non-standard script - can cause the deposit to be flagged as unrecognized.

Native SegWit (bech32) addresses start with "bc1q". They are the current standard. The design was explicitly intended to reduce ambiguity: the address encodes the witness program directly, uses a checksum that catches typos, and is case-sensitive in a way that prevents mixed-case errors. Exchangers that support SegWit (the overwhelming majority do) treat bech32 as their primary format. A deposit to a bc1q address is processed as a straightforward, low-fee transaction that the exchanger's software can parse without guesswork.

Common failure scenarios with non-bech32 addresses

• Legacy addresses sometimes trigger a "deposit not detected" error because the exchanger's monitoring node is configured to watch only SegWit outputs. The transaction confirms on-chain but never appears in the swap order.
• P2SH addresses can be misinterpreted if the exchanger expects a specific redeem script. Some services will reject the deposit outright; others will credit it but then fail to process the swap, leaving the Bitcoin stuck until support intervenes.
• Mixed-case errors are rare with bech32 because the format enforces lowercase. Legacy and P2SH addresses are case-insensitive, but some exchange systems treat uppercase and lowercase as different strings. A copy-paste error from a wallet that capitalizes the address can result in a failed deposit.

What about Taproot (bc1p) addresses?

Taproot addresses (starting with "bc1p") are newer and not universally supported by swap services. If you send to a bc1p address and the exchanger has not updated its software, the deposit will fail. Stick with bc1q unless you have confirmed the service explicitly accepts Taproot.

Practical advice before you deposit

Check the exchanger's deposit page. Most will display a list of accepted address formats. If they show only "bc1q" or "SegWit", use that. If they list multiple formats, use bc1q anyway - it is the lowest-common-denominator that works with the widest range of systems. Avoid "1" and "3" addresses unless the exchanger explicitly warns that bc1q is not supported (rare, but some older platforms still rely on legacy formats).

The core principle is simple: the fewer steps the exchanger's software must take to decode your address, the less likely it is to fail. Bech32 was designed to be decoded in one pass. Legacy and P2SH require multiple passes and fallback logic. That extra complexity is where deposits get lost.

If you want to understand why Bitcoin swaps in general take longer or cost more than trades on a single exchange, the hub page "Swapping Bitcoin for other assets" covers the underlying differences - including confirmation requirements, mempool dynamics, and the role of address formats in deposit reliability.

Back to daos