Optimism Bridge

Overview

The canonical OP Mainnet bridge uses Ethereum and Layer 2 contracts to move ETH, supported tokens, and cross-domain messages. Deposits originate on Layer 1 and create corresponding Layer 2 transactions after derivation by the rollup.

Withdrawals move in the opposite direction and require proving the Layer 2 withdrawal under the current fault-proof process before finalization on Ethereum. Third-party fast bridges may provide liquidity sooner but add separate contracts and counterparty assumptions. Users should verify official bridge interfaces, token mappings, destination, fees, and expected withdrawal stages. Applications need to track both Layer 1 and Layer 2 transaction identifiers. A deposit approval or withdrawal initiation is not the same as spendable completion on the destination.

Relevant assumptions include the validator or signer set, multisignature policy, light-client or proof design, relayers, upgrade authority, rate limits, and liquidity providers. Being described as official does not eliminate the underlying trust and control assumptions. The security model depends on the exact verification route. Routing and custody records must bind the source asset, destination representation, contract addresses, decimals, mint or custody model, and redemption path. Two assets can share a symbol while having different issuers, contracts, or backing; symbol matching alone is therefore unsafe for crediting.

Paused contracts, depleted liquidity, delayed proofs, or destination failure should enter review rather than being reported as a completed cross-chain payment. Operational support needs separate status for every stage, timeout and replay protection, route-specific monitoring, and a documented recovery path. Settlement consideration: Optimism’s canonical bridge connects Ethereum and OP Mainnet, with deposits and fault-proof withdrawals following different multi-stage lifecycles.