What is a crypto bridge?

The problem: blockchains do not talk to each other

If you hold ETH on Ethereum and want to use it on Solana, you have a problem. Ethereum and Solana are completely independent networks with different architectures, different consensus mechanisms, and different virtual machines. There is no built-in mechanism for one chain to verify what happened on another.

This is by design. Each blockchain maintains its own ledger, its own set of validators, and its own rules. Security depends on that isolation. But it also means your tokens are stuck on whichever chain they live on -- unless you use a bridge.

How bridges work: lock and mint

The most common bridge mechanism is called lock-and-mint. The process works in three steps:

1. Lock. You send your tokens to a smart contract on the source chain. The contract locks them, taking them out of circulation.
2. Verify. The bridge protocol detects that the tokens were locked. Validators, relayers, or oracles confirm the transaction.
3. Mint. The bridge mints an equivalent number of "wrapped" tokens on the destination chain and sends them to your address there.

When you want to go back, the process reverses: you burn the wrapped tokens on the destination chain, and the bridge releases the original tokens on the source chain.

The critical question is always: who or what verifies step two? That is where bridge designs diverge -- and where most security failures happen.

Types of bridges

Trusted (centralized) bridges

A trusted bridge relies on a centralized custodian or a small set of operators to verify cross-chain transactions. Wrapped Bitcoin (WBTC) is a classic example: BitGo holds the real BTC in custody and issues WBTC tokens on Ethereum. You are trusting BitGo not to lose, steal, or mismanage the underlying Bitcoin.

Centralized bridges are simpler and often faster, but they introduce a single point of failure. If the custodian is compromised, all locked assets are at risk.

Trustless (decentralized) bridges

Trustless bridges use smart contracts and decentralized validator sets to verify cross-chain messages. Protocols like Wormhole and LayerZero employ networks of independent validators (called "guardians" or "oracles") that must reach consensus before minting tokens on the destination chain.

The word "trustless" is aspirational. You still trust the smart contract code, the validator set, and the bridge's economic security model. But the trust is distributed rather than concentrated in a single entity.

Native bridges

Some blockchains have their own official bridges. The Arbitrum Bridge and Optimism Bridge move assets between Ethereum and their respective Layer 2 networks. These native bridges inherit the security of the underlying chain -- Ethereum validators verify the transactions -- making them generally safer, though slower (withdrawals from Optimistic Rollups take about seven days).

Native token transfer: no wrapping at all

The newest approach avoids wrapping entirely. Circle's Cross-Chain Transfer Protocol (CCTP) lets you move USDC natively between chains. Instead of locking USDC on one chain and minting a wrapped version, CCTP burns USDC on the source chain and mints fresh, native USDC on the destination. The result is real USDC on both sides, with no wrapped token and no locked pool to hack.

Major bridges you will encounter

Why bridges are the most hacked part of crypto

Bridges hold enormous pools of locked tokens, making them the largest honeypots in the ecosystem. They also involve some of the most complex code in crypto -- coordinating across multiple chains, managing validator sets, and handling edge cases in consensus. The combination of high value and high complexity is catastrophic from a security perspective.

Here are the largest bridge exploits in crypto history:

• Ronin Bridge -- $625 million (2022). North Korean hackers compromised five of nine validator keys. The Ronin bridge had reduced its validator set to speed up transactions, making it far easier to attack.
• Wormhole -- $325 million (2022). An attacker exploited a signature verification bug to mint 120,000 wrapped ETH on Solana without depositing anything on Ethereum. Jump Crypto backstopped the losses.
• Nomad -- $190 million (2022). A smart contract upgrade introduced a bug that let anyone copy a valid transaction and replay it with their own address. Hundreds of wallets drained the bridge in a chaotic free-for-all.
• Harmony Horizon -- $100 million (2022). The bridge used a two-of-five multisig. Attackers compromised two keys and drained the entire bridge. The funds were never recovered.

The pattern is clear: bridges fail when their validation mechanism is compromised, whether through validator key theft, smart contract bugs, or inadequate security architecture. Understanding these risk factors is essential before bridging significant value.

Wrapped tokens vs. native tokens after bridging

After you bridge, the tokens you receive are usually "wrapped" versions of the original. WETH on Solana is not native ETH -- it is a Solana token backed by ETH locked in a bridge contract. This distinction matters for several reasons:

• Counterparty risk. The wrapped token is only as safe as the bridge backing it. If the bridge is hacked, the wrapped token loses its peg and its value.
• Liquidity. Wrapped tokens may have less liquidity than native tokens, leading to higher slippage when trading.
• DeFi compatibility. Some protocols only accept specific versions of a token. Aave on Arbitrum may accept native USDC (bridged via CCTP) but not USDC.e (the older Ethereum-bridged version).

Always check which version of a token a protocol expects before depositing. Understanding token types helps you avoid costly mistakes.

How to bridge safely

Bridging will never be risk-free, but you can reduce your exposure:

1. Use official bridges for L2s. If you are moving assets to Arbitrum, Optimism, or Base, use their native bridges. They inherit Ethereum's security.
2. Start with a small test transaction. Bridge a small amount first to confirm the process works before sending significant value.
3. Check the bridge's track record. Has it been audited? How long has it been running? How much total value locked (TVL) does it hold? A bridge with $500 million in TVL and two years of operation is generally more battle-tested than a new one with $10 million.
4. Prefer native token transfers. If you are moving USDC, use CCTP where available to avoid wrapping entirely.
5. Never bridge more than you can afford to lose. This applies to all of crypto, but bridges warrant extra caution given their track record.

Bridged tokens in your portfolio

If you hold tokens across multiple chains, your portfolio likely contains bridged assets -- even if you did not bridge them yourself. Many tokens you buy on a DEX are wrapped versions that arrived via a bridge. CleanSky detects tokens across 34+ networks, including bridged and wrapped variants, giving you a clear picture of your actual holdings and the underlying bridge dependencies.

Staying informed about bridge risks is part of the broader discipline of staying safe in crypto. Combined with understanding how crypto addresses work, you will be better equipped to manage a multi-chain portfolio without falling into common traps.