At a glance
- A bridge is
- Infrastructure that moves assets or messages from one blockchain to another, which otherwise cannot see each other at all
- The usual design
- Lock the asset on the source chain and mint a matching "wrapped" token on the destination; burn it to release the original
- The token you receive
- Is an IOU on the far chain, backed by the funds locked on the near one. It is only as good as that backing
- The trust question
- Who confirms the lock really happened? A multisig, a set of validators, or on-chain proofs. That choice is the security model
- Why it matters
- Bridges concentrate enormous value behind that confirmation step, and some of the largest hacks in the space have been bridges
Chains cannot see each other
Each blockchain is its own island. Ethereum has no idea what happened on another chain, and vice versa; a contract can only read the state of its own chain. So if you hold an asset on one chain and want to use it on another, there is no native way to simply send it across. A bridge is the messenger that spans the gap: a system that observes an event on one chain and causes a corresponding action on the other. Every cross-chain move you make goes through one.
Lock and mint, burn and release
The most common design is lock-and-mint. To move a token from chain A to chain B, you send it to the bridge's contract on chain A, which locks it in custody. The bridge then mints an equal amount of a wrapped version of that token on chain B and sends it to you. The wrapped token is a claim: for as long as the original stays locked, the wrapped one represents it. To go back, you burn the wrapped token on chain B, and the bridge releases the original on chain A.
The wrapped token on the far side is, in plain terms, an IOU. Its value rests entirely on two things being true: the original really is locked, and the bridge will honour the burn to give it back. If either fails, the wrapped token can become worthless even though it still exists.
Who confirms the crossing?
The whole design hinges on one question: how does chain B know the lock on chain A actually happened, before it mints? Different bridges answer differently, and the answer is the security model.
- A trusted set. A group of validators, or a multisig, watches chain A and signs off that the lock occurred. Simple and fast, but you are trusting that group: if enough of their keys are compromised or collude, they can mint tokens that are not backed by anything.
- Cryptographic proofs. A more advanced design has chain B verify a proof of chain A's state directly, so it trusts maths rather than a committee. This is harder to build but removes the human trust point.
When you use a bridge, you are accepting its trust model whether you read it or not. "How is a mint authorised, and who could fake one?" is the question that separates a robust bridge from a fragile one.
Why bridges get drained
Bridges are among the most attacked things in the entire ecosystem, and several of the largest thefts on record have been bridge hacks measured in hundreds of millions. The reason is structural. A bridge holds all the locked assets in one place, so its custody contract is a concentrated pot of value. And the confirmation step, the part that authorises a mint, is a single high-value target: if an attacker can forge a valid-looking confirmation, whether by stealing enough validator keys or by exploiting a flaw in the proof-checking code, they can mint unbacked wrapped tokens and drain the real ones. The lesson for a user is caution: prefer well-audited, established bridges, understand what backs the token you receive, and treat any bridge as the honeypot it is.
A bridge is a honeypot by construction. It has to hold the value it moves and it has to trust something to authorise the other side. That combination is why bridges are targeted so relentlessly. Before moving significant value, know the bridge's trust model, its audit history, and exactly what your wrapped token is a claim on.
The short version. Chains cannot see each other, so a bridge carries assets across by locking the original on one side and minting a wrapped claim on the other, reversing it with a burn and release. That wrapped token is only as sound as the locked backing and the step that confirms the lock. How that confirmation is authorised, a trusted committee or a cryptographic proof, is the security model, and because bridges concentrate value behind that step, they are among the most heavily exploited targets in the space. Choose them carefully and know what backs what you hold.
References & further reading
- Ethereum community, Blockchain bridges. Designs, wrapped assets, and trust models.
- Ethereum community, Layer 2 and moving between chains. Where bridging fits in scaling.
- Ethereum community, Security and scam prevention. Caution when moving value across chains.