BlockchainIntermediate#Interoperability#Infrastructure
Cross-Chain Bridge
C
Definition
A system that transfers assets, messages, or state between blockchain environments. Its security depends on the verification model, contracts, operators, and the chains it connects.
Source reviewed
- Ethereum.org: Bridges opens in a new tab
Supports: Explains bridge designs, trust assumptions, security trade-offs, and smart-contract, financial, counterparty, and operational risks.
- Ethereum.org: Introduction to blockchain bridges opens in a new tab
Supports: Explains trusted and trust-minimized bridge assumptions and user risks including contract bugs, operator behavior, chain compromise, and user error.
Concept Diagram
Key Takeaways
1
Bridges connect otherwise separate chains, but their assets and messages use route-specific verification assumptions.
2
Lock-and-mint, liquidity-network, and message-bridge routes have different custody and failure modes.
3
Check contracts, operators, upgrade powers, audit scope, fees, slippage, representation, and withdrawal path for the exact route.
4
An audit or a familiar brand does not eliminate bridge risk.
Practical Example
Before moving an asset, a user confirms the official destination domain, the chain IDs, the exact token representation, operator and upgrade assumptions, fee, expected completion time, and a small test transaction. They do not infer safety solely from a bridge label or a prior transaction's success.
Finished learning?
Related Terms
Blockchain
Bridge RiskThe implementation, verification, custody, liquidity, and operational risks created when value or messages move between blockchains. The risk depends on the specific bridge and connected networks; no bridge type is universally safest.
Blockchain
AppChainA blockchain or rollup designed around one application or a narrow set of application logic, rather than a general-purpose smart-contract environment. Its performance, governance, and security properties depend on its specific implementation.
Blockchain
Atomic SwapA protocol for conditionally exchanging assets across compatible systems, often using hashlocks and timelocks. Atomicity applies only to the protocol's specified settlement conditions; it does not eliminate implementation, market, privacy, or legal risk.
Blockchain
Layer 2 (L2)A protocol layer that executes transactions outside an L1 while using that L1 for some combination of data availability, proofs, dispute resolution, or settlement. Fees, finality, bridges, and withdrawal paths depend on the specific L2 design.
Related Deep Dives
Master the hub of Blockchain
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles