A cross-chain transfer is complete only when the destination transaction reaches the bridge’s required confirmation threshold, not merely when the source transaction succeeds.
The detail that makes the whole process click is that “confirmed” is not one universal event. A transfer has several clocks running at once, and the destination chain usually controls the last one.
The numbers that control the handoff
- Source confirmations: how many blocks the bridge waits before accepting your deposit or burn as reliable.
- Destination confirmations: how many blocks must follow the payout, mint, or release transaction before the bridge marks the transfer complete.
- Destination block interval: the chain’s typical time between blocks, which turns a confirmation count into an approximate wait.
- Relayer or solver delay: the time between source verification and submission of the destination transaction.
- Destination transaction cost: the gas required to execute the final transaction, usually reflected in the route’s fee or spread.
A simple estimate is: completion time ≈ source wait + relayer delay + destination transaction inclusion + destination confirmations. If a destination chain produces a block every two seconds and the bridge requires 20 confirmations after inclusion, the confirmation portion is roughly 40 seconds. That is an estimate, not a promise: missed blocks, congested RPC endpoints, and a relayer waiting for more evidence can extend it.
What a destination confirmation actually measures
A destination confirmation measures how deeply the bridge’s transaction sits inside the destination chain. The first confirmation normally means the transaction was included in a block; each later confirmation is another block built on top of it.
This matters because a newly included transaction can still be affected by a short reorganization. Waiting for more blocks lowers that practical risk. It does not necessarily mean the transaction has reached the chain’s strongest form of finality. On Ethereum Mainnet, for example, blocks arrive on roughly 12-second slots, while protocol-level finality takes much longer than a handful of block confirmations. A bridge may therefore use an earlier operational threshold for speed, or wait for a stronger finalized state when the route’s security model demands it.
Confirmation terminology also varies. One service may call an included transaction “one confirmation”; another may describe “six confirmations” as six blocks after inclusion. The number is useful only alongside the chain, the counting convention, and the bridge’s completion rule.
Why the destination changes both time and cost
The destination chain decides how quickly the final transaction can be included and how much it costs to submit. A cheap, fast rollup can make the last leg inexpensive, but the bridge may still wait for the source chain or for an oracle, proof, or challenge condition. A slower or more heavily used destination can delay inclusion even after the source side is settled.
The route design matters too. Owlto Finance documents a separate destination transaction cost, which is why a quote can distinguish the service fee from the gas needed to deliver funds. Orbiter Finance describes a maker flow in which the maker observes the source payment and sends the recipient’s funds on the destination network. In both cases, the final payout is a real destination transaction with its own inclusion and confirmation lifecycle.
A successful destination receipt proves that the contract call executed. It does not by itself prove that the bridge has finished its monitoring policy. If the receipt is successful but the status remains pending, the usual explanation is that the transaction is still below the required confirmation depth or that the bridge’s indexer has not caught up.
What to check before sending
For a transfer that ends on Manta, the Manta Bridge route is the point at which the destination network, confirmation policy, and fee fields become an operational choice.
- Record the source transaction hash and verify that the source transaction succeeded.
- Find the destination transaction hash rather than relying only on the wallet balance.
- Check its block number, current confirmations, and receipt status on the destination explorer.
- Compare the observed depth with the bridge’s stated completion threshold.
- Keep a small balance of the destination chain’s gas token if you need to move or swap the received asset immediately.
The practical lesson is straightforward: source success starts the handoff; destination confirmations finish it. When a transfer appears stuck, those two facts tell you whether you are waiting for the relayer, the destination chain, or the bridge’s final safety check.
Top comments (0)