Why a Native Bridge Withdrawal Can Take Days

A native bridge withdrawal can take days because the destination chain waits for evidence that the source chain recorded a valid exit. On an optimistic rollup, that evidence must also remain unchallenged through a security window, often about seven days. The wait protects funds held on the destination chain’s bridge contract.

What happens when you start a native withdrawal?

The process begins with a transaction on the rollup. Its bridge or message contract records a request to release a specific asset to a specified address on the destination chain. The rollup processes that request, and its operator publishes a commitment to the resulting state on the destination chain.

Next, the withdrawal needs a proof that connects the request to that published state. Depending on the system, a user, relayer or bridge interface submits the proof to the destination chain’s contract. This may require a separate transaction and a network fee. The Manta bridge guide to deposit and withdrawal fees covers those costs in more detail; the fee is separate from any security delay.

Once the contract accepts the proof, it can mark the withdrawal as pending. The destination chain still needs to decide when that proof is safe to act on. Only after the required conditions are met can a final transaction release the assets.

Why does the security window last so long?

Optimistic rollups publish transaction results without first attaching a validity proof for every batch. They treat the result as correct unless someone challenges it. The challenge window gives validators and other watchers time to check the published result and submit evidence if it is wrong.

Think of it as a disputed invoice that cannot be paid until the review period ends. The bridge contract holds the funds during that period because releasing them too early could make an incorrect withdrawal difficult to reverse. On some optimistic rollups, the window is roughly seven days; it is a protocol setting, not a universal rule for every native bridge.

Other rollup designs can use validity proofs, which establish that a batch follows the chain’s rules. Those systems do not rely on the same optimistic challenge period, though proof generation, batch publication, destination-chain confirmation and a final claim can still add time. “Native” identifies the bridge’s role in the chain’s own protocol; it does not promise one fixed withdrawal speed.

What should you check while the withdrawal is pending?

Check which stage the bridge interface shows before treating a delay as a problem. A request can be recorded on the rollup while its proof is not yet available on the destination chain. After the waiting period, the claim may still need to be submitted and confirmed there.

• Confirm the source and destination networks, asset and recipient address before starting.
• Keep the withdrawal transaction details so you can look up its status on both chains.
• Check whether the interface requires a separate proof or final claim, and whether you need destination-chain funds to pay its fee.

A third-party fast bridge can sometimes pay out sooner by advancing funds from its own inventory, then settling the native withdrawal later. That convenience can cost more and depends on the provider’s liquidity and terms. For most readers, the native route is the simpler choice when the funds can remain in transit for the chain’s full settlement period. The days are part of how that route waits for an exit to become safe to finalize.