Base bridge
Base bridge withdrawals depend on proof eligibility and route liquidity
Base bridge withdrawals reach their destination through routes with different timing constraints and capacity limits. Standard withdrawals to Ethereum require proof submission and finalization, while liquidity-based routes depend on funds available for destination delivery. Compare the same destination asset and amount, then distinguish an estimated arrival from a completed transfer.
· updated
Available liquidity bounds the fast route before submission
A fast route needs enough destination liquidity to deliver the requested asset under its quoted conditions. The available amount can change as other transfers consume capital or providers replenish it. A displayed maximum therefore describes that route at the time of the quote. If the amount exceeds available capacity, pause before submission and refresh the quote or reconsider a compatible standard withdrawal.
What determines when a standard withdrawal becomes claimable?
A standard withdrawal becomes claimable when its supporting proof satisfies the applicable protocol conditions and finalization becomes available. A successful withdrawal initiation transaction on Base establishes the request; it does not establish immediate destination availability. The proof path and the request’s state determine the remaining wait.
Proof conditions determine eligibility
Base groups blocks into checkpoints, with each checkpoint represented by an output root. The withdrawal requires a proof submitted on Ethereum against an acceptable proposal covering the relevant Base state. This creates a dependency beyond the source transaction: confirmation on Base alone does not satisfy the destination contract’s proof requirements.
A single proof follows its configured window
The single-proof path retains a longer settlement window. Its duration belongs to the applicable protocol configuration, rather than a permanent rule for every withdrawal. Changes to that configuration can make older countdown descriptions inaccurate without changing the requirement for a valid supporting proposal.
Agreeing proofs can support a shorter window
The shorter dual-proof path requires both proof systems to support the same checkpoint proposal. Those systems use a trusted execution environment and a zero-knowledge proof. The shorter path depends on both systems providing valid proofs for the same proposal.
Eligibility still leaves a transaction to complete
Finalization executes the withdrawal on the destination side after the protocol permits it. A countdown reaching zero does not itself submit that transaction. The remaining time includes transaction submission and inclusion, so a protocol waiting period and total delivery time describe different intervals.
How does faster delivery change the withdrawal trade-off?
A liquidity-based route pays the recipient using available destination funds while the provider settles its position separately. This can shorten the recipient’s wait because delivery does not require the provider’s reimbursement to finish first. The arrangement adds dependencies on the route’s contracts, available liquidity, and a provider willing to fill the transfer. Its advertised speed describes a delivery expectation under those conditions, rather than a change to Base’s standard withdrawal rules.
Hold the input token and amount on Base, destination network, and destination token constant when comparing routes. Otherwise, a faster quote may describe a different transfer. Compare the amount the recipient will receive and any network charges payable separately. Liquidity utilization, destination execution costs, and provider compensation can affect the quote. An accepted smaller transfer also does not reserve capacity for another request: subsequent quotes reflect the capacity available when the provider evaluates them.
Gas funding can leave an eligible withdrawal unfinished
A withdrawal can satisfy its timing conditions while the account submitting finalization lacks destination gas funds. A balance on Base does not fund a transaction on another network. This is an account funding constraint, separate from proof eligibility or bridge liquidity. Include any remaining destination transaction in the cost comparison, and identify whether the route requires you to submit it or provides execution through another party.
Does an expired transfer mean the funds have returned?
An expired transfer can become eligible for a refund without the refund having reached its recipient. On routes with a fill deadline, an unfilled request expires when its delivery window closes under that route’s rules. Refund processing may still require settlement and an onchain payment. The expected fast delivery time therefore does not describe the fallback refund time.
Compare fallback terms before choosing a route with a deadline. Relevant terms include the refund destination, refund asset, and any action required to receive it. A pending transfer, an expired request, and a completed refund are different states. Only the refund payment establishes that the funds have returned. Until then, the original committed amount remains unavailable for a new withdrawal, even if an interface has stopped displaying its original arrival estimate.
An eligible withdrawal needs a funded finalization transaction
Consider a standard withdrawal whose waiting conditions have elapsed. Once its proof is accepted and finalization is available, submit the finalization transaction on Ethereum. A fast-route quote does not release the funds already committed to this request.
- Confirm the existing withdrawal satisfies its applicable proof and timing conditions before preparing finalization.
- Check the account submitting finalization has enough ETH on Ethereum for the estimated transaction cost, unless the selected service covers it.
- If eligibility and funding both hold, submit finalization for the existing withdrawal rather than initiating another transfer.
- If funding falls short, stop before submission, arrange destination gas funding, and reassess the estimate and withdrawal status.
- After submission, inspect the destination receipt and the corresponding asset delivery to the recorded recipient.
The normal path ends with successful destination execution and the expected delivery. A failed finalization receipt requires investigation of that transaction; a source withdrawal receipt cannot substitute for it. Waiting longer addresses a timing condition, but it does not supply missing gas funds.
Things people ask about Base bridge withdrawals
Will paying a higher network fee shorten the protocol withdrawal delay?
A higher network fee does not override the protocol’s withdrawal eligibility conditions. It may affect transaction inclusion when a transaction is otherwise valid and ready to execute. The proof requirements and applicable waiting window remain separate, so increasing a fee cannot make an ineligible finalization succeed.
Are fast-withdrawal limits the same in both directions?
Opposite transfer directions can have different available capacity and fee conditions. Each direction requires funds at its own destination, and providers may hold different balances across networks. A quote for moving an asset into Base therefore does not establish the amount available for withdrawing that asset from Base.
Could a proof dispute affect an otherwise valid withdrawal?
A dispute involving the supporting checkpoint proposal can affect when a withdrawal may rely on it. The validity of the individual source transaction does not settle the validity of every state claim supporting destination execution. The next action must follow the proposal and withdrawal status, rather than the original arrival estimate.
What happens to network fees when a finalization transaction reverts?
A reverted onchain finalization can still consume network fees for the computation it performed. The failed call does not complete the intended asset delivery. Before resubmitting, identify the failure condition and reassess eligibility and funding; repeating the same failing transaction can incur another charge without advancing the withdrawal.
Does a refund necessarily contain the token requested at the destination?
The route’s refund terms determine the returned asset and network. A route involving conversion may distinguish the original input asset from the requested destination asset. Compare those refund terms separately from the delivery quote, since a failed transfer does not establish that the requested output token will return to the sender.
When can a withdrawal quote expire before any funds move?
A quote can expire when its validity period ends before submission. That expiry concerns the proposed transaction terms, while a fill deadline concerns delivery after commitment. An expired quote requires fresh terms before proceeding; it does not by itself establish that a withdrawal exists or that funds need refunding.