Bitcoin Bridge Confirmations and Minting Delays
How many Bitcoin confirmations do bridges require? Often a few to six, while value-scaled rules can make large deposits wait longer before tokens mint.
Crypto Daybook Newsroom3 min read
How many Bitcoin confirmations do bridges require? There is no single number: many wait a few blocks, and six is a familiar convention. More blocks make a reorg—a change to recent Bitcoin history that can remove a deposit—less likely to undo the payment after tokens have been minted elsewhere.
TeleSwap checks Bitcoin deposits through an on-chain relay. For a BTC-to-teleBTC wrap, TeleSwap uses a four-confirmation threshold before proof submission, giving you a concrete wait estimate for that route.
How confirmation depth sets the minting wait
A bridge must decide when a Bitcoin deposit is deep enough to accept. Minting too early creates a mismatch: a reorg could erase the deposit while the tokens minted on the other chain remain in circulation.
The usual sequence is simple: the deposit transaction is mined, the bridge counts later blocks, and once it reaches the required depth, a proof or attestation is accepted and tokens can be minted. A confirmation count is a threshold for the bridge’s process; it is not the same as seeing the transaction included in Bitcoin’s first block.
Bitcoin targets one block about every 10 minutes. At a six-block depth, allow roughly an hour after the first confirmation, and longer if blocks arrive slowly. Actual minting can also take time after the threshold while the bridge accepts the proof or attestation.
- Fixed depth: The same number of confirmations applies to small and large deposits. A six-block rule, for instance, gives both amounts the same block-based wait.
- Value-scaled depth: The bridge requires more confirmations as the inbound value rises. THORChain’s confirmation counting waits longer for inbounds worth more than a block reward, so a large deposit can take longer than a small one on the same bridge.
- Relay finalization: TeleSwap’s relay contract sets the finalization depth before it accepts a deposit proof. Its documented wrap flow uses four Bitcoin confirmations, then requires proof submission before the wrap completes.
These settings reflect different risk and delay choices. The six-confirmation convention traces to the attacker-probability analysis in section 11 of the Bitcoin whitepaper: reversal probability falls as confirmation depth grows. It is a reference point, not a universal bridge rule. THORChain’s documentation describes value-based counting; TeleportDAO’s Bitcoin relay documentation explains the relay’s role in checking Bitcoin proofs. To estimate your own wait, find the bridge’s required depth and whether that number changes with deposit value.
Related
What happens to a bridged deposit if Bitcoin reorgs?
If a reorg removes the deposit before the bridge accepts it, the bridge should not mint from that deposit. After minting, a reorg can leave the bridge with tokens issued against a Bitcoin payment that is no longer in the accepted chain history. Waiting for more depth lowers the chance of that reversal; it does not make the chance zero.
Can I pay extra to make a bridge mint faster?
A higher Bitcoin fee may help a transaction get mined sooner, but it does not reduce the bridge’s confirmation threshold. With a fixed-depth rule, you still wait for the required blocks after inclusion. With value-scaled counting, a larger deposit can still need more blocks even when it confirms quickly.
What depth and deposit size does your bridge show for this transfer? Those details determine whether to expect a fixed wait of a few blocks or a longer value-based delay before minting.