A deposit is ready only when its source chain has enough history to trust. The wait depends on how that chain settles transactions and how much safety margin the receiving protocol requires.
What does a deposit confirmation tell you?
A confirmation means a transaction has been included in a block, a batch of transactions added to the chain. More confirmations mean more blocks have built on top of it, making a reversal less likely on chains where history can reorganise.
- Inclusion means the transaction appears in a block.
- Finality means the chain treats that block as settled.
- Safety margin means extra blocks a receiving service waits before acting.
These ideas are related, but they are not interchangeable. Bitcoin uses proof of work: miners compete to add blocks, so confidence grows as more blocks follow yours. Ethereum uses proof of stake: validators vote on blocks, and a block becomes finalized through agreement by enough staked ETH.
The Bitcoin Developer Guide explains why added confirmations reduce reversal risk. Ethereum.org describes its roughly 12-minute finality under normal conditions. A swap protocol can use its own earlier checkpoint for deposits; that checkpoint is a risk rule, not proof that the source chain itself has finalized.
Why can two source chains take different times?
Compare Bitcoin and Ethereum. Bitcoin blocks average about 10 minutes, so a three-block safety margin would take roughly 30 minutes. Ethereum slots are about 12 seconds, so five blocks would take roughly one minute. These are examples, not guaranteed deposit times.
Block counts alone can mislead. Five Bitcoin blocks and five Ethereum blocks represent very different waits, and the chosen margin can differ by protocol and chain. Chainflip monitors source-chain deposits and records them after its chain-specific confirmation window; its documentation describes the wait as a safety measure against reorganisations.
Arbitrum shows another wrinkle. It can show a transaction on its fast layer before the related data has settled on Ethereum. A service may accept a deposit based on an Arbitrum block threshold, while Ethereum settlement takes longer. So ask which event the service treats as sufficient, rather than comparing raw block counts.
What should you check before sending?
Check the source network and the required confirmation threshold for that deposit. A token name can appear on several networks, but sending on the wrong one can prevent the deposit from being recognised. When available, use the transaction record to confirm the network and wait for the service to recognise the deposit before assuming the swap has started.
For a cross-chain exchange, Chainflip native asset swaps are one way to move between native assets such as BTC and ETH without wrapped tokens. Chainflip’s deposit process depends on the source chain, so a quick wallet success message does not mean the swap is ready. The rule is simple: follow the source chain’s required safety threshold, not the fastest time shown in your wallet.