A fast confirmation and a completed withdrawal are different events.
Imagine moving a small balance from Ethereum to a scaling network, using an application there, then returning the remainder. The journey makes six terms practical: layer 1, layer 2, rollup, optimistic rollup, zero-knowledge rollup and bridge. No transfer is performed here; the example is a way to interpret network states and promises.
Locate the balance before judging the speed
Ethereum is the layer 1 in this example. A layer 2 processes activity separately while relying on the base network for specified security or settlement functions. A rollup executes transactions away from L1 and publishes commitments and the data needed for its design to Ethereum. Sharing a wallet address does not make balances on these networks interchangeable.
A bridge coordinates messages and asset accounting between environments. Depending on the route, assets may be locked and represented elsewhere, burned and released, or exchanged against another participant's liquidity. The receiving asset's network and contract identity matter, even when the interface displays a familiar ticker. A bridge is a mechanism with its own assumptions, not a teleport button.
Ask what has been proved, and where
An optimistic rollup can submit a claimed execution result that remains subject to a challenge process. Its canonical withdrawal route typically requires the relevant challenge period to finish before assets can be released on L1. An immediate L2 confirmation therefore does not mean an immediate completed L1 withdrawal. The precise delay and steps belong to the deployed protocol.
A zero-knowledge rollup uses validity proofs to demonstrate that a proposed state transition follows its execution rules. Proof generation, publication and verification still take time. The label does not mean every transaction is private, nor that withdrawals or bridges are universally instant. Both rollup types can also have upgrade controls and operator dependencies worth understanding separately from their proof design.
Read a withdrawal as a sequence of states
Suppose a learning application displays a balance on an imaginary optimistic L2. A user initiates a withdrawal through that L2's canonical bridge. The L2 includes the request, but the user does not yet have a spendable L1 balance. The relevant result must be posted and pass the bridge's proof and waiting requirements; a final claim or completion step may follow.
Now compare a third-party route advertising a faster exit. A liquidity provider might pay on the destination before recovering funds through the canonical route. That changes who supplies the immediate funds and adds that route's fees and risks. It does not abolish the canonical protocol's waiting requirement. Network availability, bridge code, operator controls and destination liquidity can each affect the experience.
| Interface state | What it establishes |
|---|---|
| Request included on L2 | The withdrawal request is recorded there |
| Relevant state accepted on L1 | The rollup's settlement conditions have advanced |
| Bridge completion confirmed on L1 | The destination accounting change has occurred |
Check your understanding
A wallet shows the same address on Ethereum and an L2. Are both balances available for the same transaction?
No. Each network maintains its own state. The selected network determines which balance and contracts a transaction uses; crossing networks requires an appropriate transfer or messaging route.
Check the primary sources
These references explain the rules behind the lesson. The examples above are fictional teaching scenarios written for this dictionary.