Bridge
System to transfer assets or messages across chains.
A blockchain bridge is a system that transfers information or economic value between networks that do not natively share state. It can make a token usable on another chain or pass a message that triggers a remote contract. Assets do not literally travel between ledgers; contracts and operators coordinate corresponding lock, mint, burn, release, or liquidity actions.
A lock-and-mint bridge escrows a token on the source chain and issues a wrapped representation on the destination. Returning it burns the wrapped token and unlocks the original. Liquidity-network bridges instead pay the user from destination-chain liquidity and later rebalance. General message bridges carry arbitrary instructions, making them useful for cross-chain governance and applications but expanding the impact of a verification failure.
Bridge security depends on how the destination verifies the source event. Designs may use a multisig or external validator set, a light client that checks consensus, zero-knowledge proofs, optimistic claims with challenge periods, or native rollup contracts. Each has different trust, cost, latency, and upgrade assumptions. A canonical bridge is maintained as part of a rollup system, but its admin controls and code still deserve review.
Bridges matter because users and applications operate across fragmented networks. They move stablecoins to cheap execution layers, connect liquidity, and let contracts coordinate. The wrapped destination asset is not always equivalent to the original. Its value depends on bridge solvency, redemption, contract security, and the continued operation of both chains.
Cross-chain bridges have been frequent attack targets because they custody large amounts and must correctly interpret two complex systems. Compromised keys, forged messages, replay bugs, unsafe upgrades, and chain reorganizations can create unbacked tokens or drain escrow. Fake bridge websites also steal approvals and deposits. Audits reduce risk but do not guarantee safety.
Before bridging, verify the exact source and destination networks, official interface, token contracts, minimum received, fees, and expected completion time. Test with a small amount and retain the transaction identifiers from both chains. Understand whether recovery or support is possible if a message stalls. For large transfers, consider rate limits and route concentration. A cheap, fast bridge may achieve speed by adding trusted intermediaries, so compare security models rather than selecting solely by quoted output.
Frequently asked questions
- A bridge observes or verifies an event on a source chain, then authorizes a related action on a destination chain. It may lock canonical tokens and mint wrapped representations, burn representations and release escrow, or use liquidity providers for faster swaps. Verification can rely on native rollup contracts, light clients, external validators, multisigs, or optimistic challenges.
- Bridge contracts and validators control valuable assets and have suffered major exploits. Risks include faulty message verification, compromised signer keys, malicious upgrades, replay attacks, source-chain reorgs, weak wrapped-token backing, and destination-chain failure. Prefer well-reviewed canonical routes when suitable, verify contracts and networks, limit transfer size, and understand exactly who can stop or redirect messages.
- A bridge may wait for source-chain finality, validator signatures, liquidity, rate limits, or fraud-proof challenge periods before releasing funds. Optimistic rollup exits through the canonical bridge can take days so disputed state roots can be challenged. Fast bridges may advance liquidity for a fee, adding provider and contract risk rather than removing the underlying settlement delay.