Bridge

Overview

Why Bridge matters

A blockchain cannot simply assume that another blockchain's reported state is authentic. Applications need a mechanism to verify or trust remote events and safely act on them. Bridges address this interoperability gap, making it possible to reach different networks without permanently selling the original economic position in every case.

How it works

A typical bridge flow begins with a deposit or burn on a source chain. A verifier, contract, validator committee, light-client mechanism or proof system establishes that the event occurred under the bridge's finality rules. A destination component then releases or mints a corresponding asset or delivers liquidity. Withdrawals may be subject to fraud-proof windows or other settlement delays. In designs that issue wrapped assets, a destination token's value depends partly on the collateral, custody and redemption pathway behind it. Bridge operators may have emergency pause rights, upgrade keys or concentration in attestation signers. These details determine whether the system is meaningfully decentralized and how funds can be recovered.

Canonical bridges, liquidity bridges and wrapped assets

The word bridge describes several implementations. A canonical rollup bridge generally connects that rollup with its parent settlement chain according to protocol-defined message rules. A liquidity bridge can pay the destination user from a provider's existing funds and settle or rebalance later. A lock-and-mint system may issue a wrapped token representing an asset held elsewhere. These mechanisms imply different fees, speeds and risks. A fast quoted transfer might rely on a liquidity provider's solvency and availability rather than immediate protocol-level completion. A wrapped token can also trade at a discount if its redemption channel becomes doubtful. For merchant payments, the final asset must be explicitly on the accepted list; otherwise an apparently successful bridge could deliver a representation the merchant cannot safely use.

A real-world payment example

A company wants to move treasury funds from Ethereum Mainnet to Arbitrum. It compares available bridge routes, checks which output token will be received and how long the withdrawal path takes. After arrival, treasury staff reconcile the source transaction, bridge message and destination balance as separate records. A successful deposit alone is not proof that the destination payout has completed.

Limits and common misunderstandings

Bridge contracts and signing infrastructure can be highly valuable attack targets. Even a technically sound destination chain cannot fix a compromised cross-chain proof or private key used by the bridge. Use official route information and test with small amounts when operationally justified.

How it differs from related concepts

Bridge connects ledgers; exchange converts assets; rollup is a distinct execution environment. Some products combine all three functions, but the user should distinguish them.

Explore further

Official background: technical documentation.

Related glossary terms: Cross-Chain Transfer, Wrapped Token, Bridge Security.