Cross-Chain Records Before You Use a Route
A cross-chain route adds timing, assumptions, and records that need to match before you rely on it.
Start with public records
What finality changes
Ethereum and Base both distinguish between inclusion and stronger forms of finality. For Base, regular L2 transactions and L2-to-L1 withdrawals do not share the same waiting pattern.
- Base documents that withdrawals from Base to Ethereum require a 7-day wait.
- Regular Base transactions do not require that same 7-day withdrawal window.
- Ethereum finality is the stronger state where reversion becomes economically prohibitive.
Source note
Bridge checklist
A bridge transaction is only simple when every routing assumption is explicit.
- Check the exact token on both sides of the bridge, including any wrapped version you will receive.
- Verify the destination address on the destination chain, not just the source chain.
- Wait through the documented window instead of resending from a second tool out of impatience.
Source note
Red flags
Bridge errors often come from impatience or wrong-chain assumptions.
- A tool cannot clearly explain the settlement path.
- You are asked to 'speed up' a withdrawal by sending more funds to another address.
- You cannot verify the bridge route in an official explorer or documentation page.
On this page
How to use this guide
Check the source before you respond or connect.
Compare the source you plan to use against this briefing. Confirm it independently, and stop if the public record does not match the message.
Primary sources