Arbitrum Bridge

Overview

A deposit from Ethereum locks or transfers assets through gateway contracts and creates the corresponding asset representation on the selected Arbitrum chain. The process requires Ethereum confirmation and successful message execution on Arbitrum. A withdrawal begins on the Arbitrum side and later becomes claimable on Ethereum according to the chain’s settlement model. Optimistic rollup withdrawals can include a dispute period before final execution. Faster third-party bridges use separate liquidity and security assumptions and should not be confused with the canonical bridge.

Token mapping matters. Some assets have custom gateways or canonical representations, while unsupported tokens can require special handling. The same symbol can identify different contracts across chains.

Applications should track both source and destination transaction identifiers and every message status. A successful source transaction does not guarantee final destination completion. Retryable or delayed messages can require additional actions. Users need enough native gas asset on the chain where they perform each step. Contract upgrades, paused routes, and network incidents can affect availability.

The Arbitrum Bridge is infrastructure for cross-layer movement, not a normal exchange withdrawal. Its safety depends on correct gateway contracts, rollup settlement, message execution, and user verification of the complete route. Refund and retry behavior should be designed before integration. Cross-layer messages can fail because of gas parameters, token gateway issues, or recipient contract behavior. The original asset may remain recoverable, but the resolution path can require a later transaction. Support tools should expose message identifiers and claim status rather than showing only the source transaction hash.