What Are Cross-Chain Bridges? How They Connect Blockchains

A cross-chain bridge is a protocol that lets value and information move between two separate blockchains that would otherwise have no way to communicate. Because networks like Bitcoin and Ethereum run on different consensus rules, a token cannot natively travel from one to the other. A bridge solves this by locking an asset on the source chain and issuing an equivalent representation on the destination chain. This unlocks liquidity, lets one chain's assets power another chain's DeFi apps, and is a core piece of the multi-chain economy.

📷 simple diagram showing Chain A and Chain B connected by a bridge, with a token locked on A and a wrapped version minted on B

Why Blockchains Need Bridges

Every public blockchain is, by design, a self-contained ledger. The same isolation that makes a network secure also makes it siloed — a wallet on one chain cannot see balances or call smart contracts on another. As capital and applications spread across dozens of Layer-1 and Layer-2 networks, that isolation became a bottleneck. Users wanted to take an asset that holds enormous value on one chain, such as BTC, and put it to work in a richer application ecosystem, such as Ethereum's lending and trading markets. Bridges are the connective tissue that makes this possible.

The practical jobs a bridge performs include:

• Moving tokens from a chain with deep value but few apps to a chain with a mature app layer.
• Letting a single dApp deploy and operate across multiple networks.
• Offloading transactions onto cheaper or faster chains while keeping a link to the main chain.
• Passing arbitrary data — price feeds, governance votes, contract calls — not just assets.

How a Cross-Chain Bridge Works: Lock-and-Mint

The most common mechanism is lock-and-mint (also described as a two-way peg). When you bridge an asset, nothing is literally "teleported." Instead, the original tokens are frozen in a contract or custodian on the source chain, and an equal number of wrapped tokens are created on the destination chain. To move back, you burn the wrapped tokens and the originals are released.

Step by step, a typical lock-and-mint transfer looks like this:

1. You deposit the asset into the bridge contract on the source chain.
2. The tokens are locked (held in custody and removed from circulation on that chain).
3. The bridge's validators or relayers confirm the deposit.
4. An equivalent wrapped token is minted to your address on the destination chain.
5. To reverse the trip, you burn the wrapped token; the bridge then unlocks the original.

📷 flow chart of the five lock-and-mint steps, deposit → lock → verify → mint → use

The total supply is supposed to stay balanced: for every wrapped token in existence, one real token sits locked as backing. If that 1:1 invariant breaks — through a bug or an exploit — the wrapped asset can lose its peg, which is the single biggest danger in bridge design.

Trusted vs Trustless Bridges

Bridges differ mainly in who you have to trust to keep the locked collateral safe. They fall into two broad camps.

A trusted bridge relies on a central party to hold the locked assets and issue the wrapped version. WBTC is the classic case: BTC is deposited with a custodian, and an ERC-20 representation is minted on Ethereum so it can be used as collateral across DeFi protocols. It is easy to use, but you are trusting the custodian.

A trustless bridge removes the single point of failure by distributing custody across many independent nodes that must reach consensus before assets unlock. Trust shifts from a company to math and code — the same principle that secures the underlying chains. The trade-off is greater technical complexity and a larger attack surface in the bridge software itself.

Worked Example: Bridging 2 BTC to Ethereum

Suppose you hold 2 BTC and want to lend it on an Ethereum money market. Native BTC can't enter Ethereum, so you bridge it.

• You deposit 2 BTC into a custodial bridge.
• The custodian locks your 2 BTC and mints 2 wrapped BTC (an ERC-20) to your Ethereum wallet.
• You supply those 2 wrapped BTC to a lending protocol. At, say, a 3% supply APY, that position earns roughly 0.06 wrapped BTC over a year, while your collateral can also back a stablecoin loan.
• When you exit, you burn the 2 wrapped BTC, and the bridge unlocks your original 2 BTC.

The key insight: the BTC never left Bitcoin. It sat locked the entire time, while a mirror asset did the work on Ethereum.

Sidechain Bridges

Not every bridge connects two unrelated networks. A sidechain bridge links a parent chain to a child chain that has its own validators and consensus but inherits or borrows context from the parent. Because the two run different rules, a bridge is still required to pass assets between them. A sidechain typically exists to add scalability — it absorbs transaction load so the main chain stays lighter. Game and app ecosystems have historically spun up dedicated Ethereum-linked sidechains, with a bridge handling deposits and withdrawals of ETH, ERC-20 tokens and NFTs in and out of the sidechain's contracts.

Bridging Across Ecosystems Like Polkadot

Some networks are built from the ground up to be interoperable. In a hub-and-spoke design, sovereign Layer-1 chains called parachains run in parallel and share the security of a central relay chain, while message-passing channels let them exchange data and assets trustlessly. Opening such a channel often requires a refundable deposit and a recognized, one-directional link between the two chains. These purpose-built interoperability layers point toward a future where bridging is a native feature rather than a bolted-on add-on.

📷 hub-and-spoke diagram with a central relay chain and several parachains exchanging messages

Risks and Pitfalls

Bridges concentrate a lot of locked value in a small amount of code, which is exactly why they have been among the most targeted parts of crypto.

• Smart-contract exploits. A single flaw in the lock or mint logic can let an attacker print unbacked wrapped tokens or drain the collateral pool.
• Validator or custodian compromise. If the entities that authorize unlocks are bribed, hacked, or collude, funds can be released improperly.
• De-pegging. If the 1:1 backing breaks, the wrapped asset trades below the original and may not be redeemable at par.
• Liquidity and slippage. Thin bridge liquidity can cause unfavorable rates on large transfers.
• Re-org and finality gaps. A transfer confirmed on the source chain before true finality can, in rare cases, be reversed.

Practical defense: prefer bridges with audited contracts and a long, incident-free track record; move large amounts in stages; verify you are on the official bridge URL; and never assume a wrapped token is risk-free just because the price is pegged.

COINOTAG Perspektifi

Bridges are infrastructure, not investments — and they should be evaluated like infrastructure. The most important question is not "how cheap is the transfer" but "what exactly am I trusting, and what happens if it fails." A trusted bridge collapses the entire risk down to one custodian; a trustless bridge spreads it across validators and code but adds complexity. For most users moving meaningful size, the rational path is the boring one: established bridges, multiple smaller transfers instead of one large one, and treating any wrapped asset as a claim that is only as good as the system backing it. Interoperability is unlocking real value across chains, but in this corner of crypto, security track record matters more than features.

For deeper reading, see our overview of how Ethereum scales and our guide to stablecoins, since many cross-chain flows ultimately settle in stable assets.