When is a crypto deposit safe to credit?
A deposit you can see is not yet a deposit you can keep. What confirmations, reorgs and finality mean, and what each chain's documentation tells you to wait for.
By Nasfam Business engineering,
On this page
Seen is not final
A deposit passes through stages before it belongs to you. It is broadcast and waits in the network's pool of unconfirmed transactions, where it can be dropped or replaced. It is included in a block, its first confirmation. Each later block builds on that one. At some point the chain's rules make it final: it can no longer be undone without breaking the chain itself.
Credit a deposit before that point and you are lending the customer money against a transaction that can still disappear. If they spend or withdraw the credit and the deposit vanishes, the loss is yours.
The whole question is where that point is on each chain, and how your system knows it has been reached.
What a reorg does
Two valid blocks can be produced at the same height. For a short while nodes disagree about which one is the tip. When the network settles on one branch, the blocks on the other are discarded, and so is everything they held. This is a reorganisation, or reorg.
A transaction in a discarded block is not always lost: it often returns to the pool and lands in a later block. But if a conflicting transaction spending the same funds made it into the winning branch, the deposit is gone for good. That is how a double spend works, by accident or on purpose.
Bitcoin's developer guide puts the accidental case plainly: "the most recent block gets replaced fairly often by accident, so a double spend is still a real possibility." Deliberate reorgs are rarer and cost the attacker real resources, which is why the depth you wait for should grow with the value at risk.
Two kinds of finality
Probabilistic finality. On a proof-of-work chain such as Bitcoin, every block on top of yours makes a reversal less likely, but never impossible. There is no moment the protocol calls final; you choose a depth that makes the risk acceptable for the amount. Bitcoin's guide suggests that software handling high-value or fraud-prone payments "should wait for at least six confirmations", and calls that number "somewhat arbitrary".
Deterministic or economic finality. Most proof-of-stake chains reach a point where a block is final by the protocol's own rule: a supermajority of validators has voted on it, and reverting it would require breaking the chain's guarantees or destroying a large share of the stake. On these chains, counting blocks is the wrong instrument. Ask the chain whether the block is final, through the finality signal it publishes, and wait for that.
Layer 2 rollups add a third idea. A sequencer can confirm a transaction in well under a second, but that promise is only as strong as the sequencer until the transaction's batch is posted to the parent chain and that parent block is itself final.
What each chain's documentation says
The table summarises what each chain's own documentation says, read on 12 November 2026. It is a starting point for your own reading, not a substitute for it: chains change their consensus, and the documentation changes with them. Times are the documentation's typical figures, not guarantees.
| Chain | Wait for | What its documentation says |
|---|---|---|
| Bitcoin | A depth you choose for the value at risk | No protocol finality. High-value payments "should wait for at least six confirmations", a number the guide calls "somewhat arbitrary". |
| Ethereum | The finalized block | Finality comes from checkpoints that two-thirds of the staked ether votes for. "It takes about 15 minutes for an Ethereum block to finalize." The JSON-RPC latest block "may be re-orged out of the canonical chain even under healthy/normal conditions". |
| OP Stack chains (OP Mainnet) | The finalized block | A block is unsafe until its data is posted to Ethereum, safe once it is, and finalized when that Ethereum block is finalized, typically within about 15 to 30 minutes of submission. |
| Base | L1 batch finality | An OP Stack chain. Its own page describes the stages by time: in an L2 block, the batch posted to Ethereum, then the batch older than two epochs, about 20 minutes in all. |
| Arbitrum One | The finalized block | "An Arbitrum block is only as final as the parent-chain block that carries its batch." The sequencer's soft confirmation is "fast (sub-second) but reversible". |
| BNB Smart Chain | The finalized block | Finalized "within two blocks if ⅔*N or more validators vote normally". With too few votes it falls back to probabilistic finality. |
| Polygon PoS | The finalized block | Milestones "typically finalize a transaction within 2 to 5 seconds", and once a block is finalized there is no chance of a reorganisation. |
| Solana | The finalized commitment | processed "can still be rolled back"; confirmed has been voted on by more than two-thirds of the active stake; finalized has reached maximum lockout, the strongest state. |
| TRON | A solidified block | A block is solidified, "final on-chain and cannot be replaced by a fork", once at least 19 distinct active super representatives have produced a block at that height or above, typically in about a minute. |
| TON | Inclusion in a masterchain block | Finality comes "after a single masterchain block confirmation, typically within 1 second". A transaction seen only in a shardchain block is not yet final. |
On every chain in the table that publishes a finalized tag or commitment, your node or data provider can answer the question directly. Ask for the finalized block and compare heights, rather than keeping your own count of confirmations and hoping it matches the protocol's rule.
Where the documentation disagrees or is silent
- Ethereum's time to finality is "about 15 minutes" on ethereum.org. Arbitrum's page, describing the same finality, says about 13 minutes; the OP Stack's says two to three epochs, about 13 to 19 minutes, and that finality "can take longer during adverse network conditions on Ethereum". None is a promise. Design for a wait you cannot bound.
- Bitcoin's documentation names no depth per amount. Six confirmations is a convention its own guide calls arbitrary; the right depth is a risk decision you make and write down.
- Solana gives no time to finality, and its pages pull in two directions: the deposit section of its exchange guide polls
confirmedblocks, while its RPC documentation describesfinalizedas the strongest state. For money you will let a customer withdraw,finalizedis the conservative reading. - BNB Smart Chain's two blocks hold only while two-thirds of validators vote. The documentation gives no number for the fallback case, so a system that counts blocks there has no documented safe count.
- Base describes its stages by how many minutes each takes, and does not use the unsafe, safe and finalized names the OP Stack documentation uses for the same stages.
Designing a deposit flow around finality
- Keep two states. A deposit is first detected, then credited. Show a detected deposit to the customer as pending, never as spendable balance.
- Read finality from the chain. Ask for the finalized block, commitment or solidified height the chain publishes, and credit only deposits at or below it. Where the chain has no such signal, wait the depth your written policy sets for that amount.
- Follow block hashes, not heights. A height can be filled by a different block after a reorg. Keep the hash of the block each detected deposit is in, and if that block leaves the canonical chain, move the deposit back to detected.
- Match everything, not just the amount. The asset by its contract or token address, never by its symbol, which anyone can copy; the destination address; and the memo or tag where the chain uses one to tell customers apart.
- Make crediting idempotent. Key each credit by the chain, the transaction hash and the output or log index, so a rescan, a restart or a duplicate notification can never credit the same deposit twice.
- Keep one rule per chain, in one place. A multi-chain system that spreads finality rules across services will eventually treat one chain by another's rule. One table, one owner, reviewed when a chain changes its consensus.
Do not move a deposit onward, by sweeping it or paying it out, until it is final. A sweep built on a deposit that is later reorged away is a second problem on top of the first; the sweeping guide covers why.
If a credited deposit disappears
If you credit before finality, a reorg can remove a deposit your ledger already counts. The balance is then wrong, and the customer may already have spent it. You need a written path for this before it happens: stop further withdrawals on the affected balance, confirm the deposit is truly gone from the canonical chain rather than merely delayed, and reverse the credit with a recorded ledger entry that names the reason. Never correct a balance by editing it in place.
The cheaper path is to not need any of that: credit at finality, and let the pending state carry the wait.
Sources
Each was read on 12 November 2026. Where a quotation appears in the guide, it is that page's own words.
- Bitcoin developer guide: payment processing. Six confirmations, "somewhat arbitrary", and accidental replacement of the latest block.
- Bitcoin developer guide: block chain. How forks resolve to the chain with the most work, and stale blocks are discarded.
- ethereum.org: proof-of-stake. Checkpoints, justification and finalization by two-thirds of the staked ether.
- ethereum.org: single slot finality. About 15 minutes for a block to finalize.
- Ethereum execution APIs: block tags. The definitions of
latest,safeandfinalized. - OP Stack: transaction finality. Unsafe, safe and finalized blocks; about 15 to 30 minutes to finalized; Ethereum finality in two to three epochs, longer in adverse conditions.
- Base: transaction finality. The stages to L1 batch finality, by time.
- Arbitrum: finality and reorgs. Soft confirmation, and finality tied to the parent-chain block carrying the batch.
- BNB Chain: BNB Smart Chain introduction. Fast finality within two blocks, its condition, and the fallback.
- BNB Chain: BEP-126, fast finality. The fast finality mechanism.
- Polygon: PoS finality. Milestones, 2 to 5 seconds, and querying the finalized block.
- Solana: RPC commitment levels.
processed,confirmedandfinalized. - Solana: exchange integration. Polling confirmed blocks to track deposit accounts.
- TRON: consensus. Solidified blocks and the 19 of 27 super representatives.
- TON: payments overview. Finality after one masterchain block, and checking the masterchain rather than a shardchain.
Keep reading
Sweeping deposit addresses safely
Gas on token-only addresses, dust and gas griefing, batching, and why only final funds are swept.
Reliable payment webhooks
Signatures, replay protection, consumers that are safe to call twice, retries and dead letters.
