bridges
Bridges are protocols that allow the transfer of tokens, data, or instructions between different blockchains or Layer-2 networks.
Blockchain bridges are interoperability protocols designed to facilitate the transfer of assets, data, or arbitrary instructions between two or more independent blockchain networks. These networks can be Layer-1 blockchains (e.g., Ethereum, Bitcoin) or Layer-2 scaling solutions (e.g., Polygon, Arbitrum). The core challenge bridges address is the inherent isolation of blockchain ecosystems, which typically lack native mechanisms for cross-chain communication. Bridge architectures vary significantly, broadly categorized into trusted (or centralized) and trustless (or decentralized) models. Trusted bridges rely on a central intermediary or a federation of validators to manage asset transfers, often involving locking assets on the source chain and minting equivalent wrapped assets on the destination chain. This model offers simplicity and speed but introduces counterparty risk and censorship potential. Trustless bridges, conversely, employ cryptographic proofs, smart contracts, and often light clients or relayers to verify events on one chain and trigger actions on another without a central point of failure. Examples include optimistic bridges, which assume validity until challenged, and ZK-rollup-based bridges, which use zero-knowledge proofs for enhanced security and efficiency. Key trade-offs involve security assumptions, transaction finality, cost, speed, and the complexity of implementation and user experience. Vulnerabilities often lie in the smart contract logic, validator collusion, or the underlying security of the connected chains.
graph LR
Center["bridges"]:::main
Rel_blockchain_interoperability_security["blockchain-interoperability-security"]:::related -.-> Center
click Rel_blockchain_interoperability_security "/terms/blockchain-interoperability-security"
Rel_chainlink["chainlink"]:::related -.-> Center
click Rel_chainlink "/terms/chainlink"
Rel_cross_chain_bridge["cross-chain-bridge"]:::related -.-> Center
click Rel_cross_chain_bridge "/terms/cross-chain-bridge"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧠 Knowledge Check
🧒 Explain Like I'm 5
Imagine different countries with their own money. A [bridge](/en/terms/bridge) is like a special exchange office that lets you swap your money from one country for the money of another country, so you can use it there.
🤓 Expert Deep Dive
Interoperability solutions, commonly termed bridges, are critical infrastructure for a multi-chain future. Architecturally, they can be classified by their security model: federated (multi-sig or committee-based), relayer-based (monitoring events and submitting proofs), or light-client based (verifying headers on-chain). Atomic swaps, while a form of cross-chain interaction, are typically peer-to-peer and do not involve intermediate protocols for asset bridging. More advanced bridges leverage ZK-proofs (e.g., ZK-SNARKs/STARKS) to generate validity proofs of state transitions on one chain, which are then verified on the destination chain, offering high security with minimal trust assumptions. The "trusted" component often relates to the mechanism of asset minting/burning or the validation of off-chain events. For instance, a common pattern involves locking an asset on Chain A and minting a synthetic representation on Chain B. The security of this synthetic asset is paramount and depends on the integrity of the locking mechanism and the minting/burning contract. Edge cases include chain reorganizations, reentrancy attacks on the bridge contracts, and economic exploits targeting the collateralization or reward mechanisms of the bridge operators.