Bridges explained: your coins stay in a strongbox, you travel with an IOU
A blockchain bridge doesn't move coins between chains. It locks them on one chain and issues a matching token on the other, or swaps them through someone else's pool. What you hold on the far side is a claim, and it's only as good as whoever guards the locked coins.
Between the village and the town across the river runs a ferry. But the ferry office doesn't carry your coins. It locks them in a strongbox on this bank and hands you a paper on the other: "Good for 10 coins, redeemable at the ferry office."
In the town, people accept the paper because they believe the strongbox is full. Come back, hand in the paper, and the office opens the box and gives you your coins.
The stranger at the gate has a faster ferry, of course. No strongbox needed, he says, just hand him the coins. That's the question for every bridge: who holds the strongbox, and how would you know if it's empty?
What it is
A bridge connects two blockchains that can't read each other's notebooks. ethereum.org lists the main designs (ethereum.org):
- Lock and mint: "Lock assets on the source chain and mint assets on the destination chain." The token you receive is a wrapped token, an IOU.
- Burn and mint: "Burn assets on the source chain and mint assets on the destination chain." Used where one issuer controls the token on both sides. The way back of a lock-and-mint bridge works the same way in reverse: burn the IOU, release the original.
- Liquidity networks: bridges that move value "via atomic swaps". You hand coins to a pool on one chain, someone pays you from a pool on the other.
Then there's the question of who checks. ethereum.org splits bridges into trusted ones, which "are externally verified" by a group such as a multisig or federation, and trustless ones that rely only on the two chains themselves. A rollup's own bridge to Ethereum is the second kind; "Layer 1 vs layer 2" timed its walk home.
How it works: check the strongbox
Take a real ferry office: the peg between Bitcoin and Liquid, the sidechain from "Sidechains explained". An 11 of 15 federation guards the bitcoin locked on the Bitcoin side (Liquid docs). The Liquid explorer publishes both sides of the ledger. Read on 19 November 2026 (liquid.network):
- Paper in circulation: 4,249.97 L-BTC on Liquid, at Liquid block 4,152,234.
- Coins in the strongbox: 4,252.91 BTC in the federation's addresses, at Bitcoin block 976,601.
- The difference: 4,252.91 minus 4,249.97 is 2.94 BTC more in the box than paper outstanding (the page shows 2.93, from unrounded figures). Holdings are about 100.07% of the paper.
That's what a working lock-and-mint bridge looks like: every IOU matched by a locked coin, and anyone able to check. Now notice what the sum doesn't tell you. It says the box is full. It doesn't say who holds the key. Here, 11 signatures out of 15 can move the coins. On other bridges it's a contract, a committee or a company. Rootstock's peg keeps its keys in hardware devices whose operators "do not directly control the Bitcoin multisig private keys" (Rootstock).
Those are examples, not recommendations. The point is the method: paper on one side, coins on the other, keys in someone's hand.
Why it matters
- Users can use a coin from one chain in another chain's apps, such as bitcoin on a smart-contract chain.
- Bridge operators earn fees and guard large strongboxes. One box holding everyone's coins is a single, very attractive target.
- Everyone holding the IOU shares the risk. If the box is emptied, the paper on the far side can lose its backing all at once. ethereum.org calls this systemic risk: "we have seen wrapped versions of tokens exploited."
Where people get it wrong
- "The bridge moved my coins." Nothing crossed. Your coins sit locked on one side; you hold a token on the other.
- "Wrapped bitcoin is bitcoin." It's a claim on bitcoin held by someone else. Two wrapped tokens from two bridges are two different claims.
- "An audited bridge is safe." ethereum.org: "all it takes is one flaw in a smart contract". An audit lowers the odds, it doesn't remove them.
- "Fast bridges are the same thing, quicker." A liquidity bridge pays you from its own pool. You trust its pool and its contracts instead of a strongbox.
Look for the audit page
Before you bridge, find the page where the bridge shows its locked coins next to its tokens in circulation, and the page that says who can move the locked coins. If you can't find either, you're trusting the ferry office on its word.
And if a stranger at the gate offers a ferry with no strongbox at all, that's not a bridge. That's a donation.
Frequently asked questions
What is a blockchain bridge?
A bridge connects two blockchains so value can move between them. Usually it locks coins on one chain and issues a matching token on the other, or swaps coins between pools on both chains. You end up holding a claim on the far side, not the original coin.
What does lock and mint mean?
The bridge locks your coins on the source chain and mints the same amount of a wrapped token on the destination chain. To go back, you burn the wrapped token and the bridge releases the original coins. The wrapped token is only as good as the locked coins behind it.
What is the difference between trusted and trustless bridges?
Trusted bridges rely on an outside group, such as a multisig, a federation or a committee, to confirm what happened on the other chain. Trustless bridges rely only on the two chains' own rules, as with a rollup's official bridge to Ethereum.
How can I check if a bridge is fully backed?
Look for a page showing the coins locked on the source chain next to the tokens in circulation on the other chain, with addresses you can check on a block explorer. On 19 November 2026, the Liquid explorer showed 4,252.91 BTC held against 4,249.97 L-BTC issued.
Are blockchain bridges safe?
They carry extra risks: bugs in their contracts, stolen or misused keys, and the failure of whoever verifies transfers. Some of the largest crypto thefts have hit bridges. Check who holds the keys, how many must agree, and whether the backing is visible.

