Short answer: a bridge locks or burns your asset on one chain and issues a matching representation on another. Because most bridges hold large pooled balances behind a small set of keys or contracts, they have been the single most exploited category of infrastructure in crypto. For a plain balance move, a direct swap is usually simpler and avoids that surface entirely.
Why bridges exist
Blockchains are isolated by design. Ethereum cannot read Solana's state, and Bitcoin cannot verify anything happening on Tron. If you hold ETH and want to use an application on another chain, something must stand between the two ledgers and guarantee that value entering one side is matched by value leaving the other. That something is a bridge.
Three models
| Model | How it works | Key risk |
|---|---|---|
| Lock and mint | Assets are locked on the source chain; a wrapped token is minted on the destination | The locked pool is a single large target |
| Burn and mint | Tokens are destroyed on one chain and reissued on another by the issuer | Requires trusting the issuer's control |
| Liquidity network | Pools on both chains; you deposit one side and a market maker pays out the other | Liquidity depth, slippage, operator solvency |
Validation matters just as much as the model. Some bridges are secured by a multisig of a handful of signers, others by an external validator set, others by light-client proofs verified on-chain. The last is the strongest and the rarest, because it is the hardest to build.
Why they get hacked so often
- Concentrated value. A bridge holds the collateral for every wrapped token it has ever issued. That is a bigger prize than almost any individual protocol.
- Complex verification code. Proving that an event happened on a foreign chain is subtle, and subtle code has more places to be wrong.
- Key management. Several of the largest losses came from compromised signer keys rather than from a flaw in the contract itself.
- Upgrade paths. An upgradeable bridge contract is only as secure as whoever controls the upgrade.
The largest bridge exploits have each removed hundreds of millions of dollars, and in most cases the funds were unrecoverable.
Wrapped tokens are IOUs
A wrapped asset on a destination chain is a claim on collateral held elsewhere. If that collateral is stolen or the bridge stops honouring redemptions, the wrapped token can trade far below the asset it represents — while the underlying asset itself is entirely unaffected. Knowing which version you hold is not a technicality.
Practical guidance
- Prefer a swap for simple moves. Sending USDT on Tron and receiving USDT on Arbitrum through an exchange service involves no wrapped token, no contract approval and no locked pool.
- Use canonical bridges where a chain provides one, rather than a third-party alternative with better marketing.
- Check who can upgrade the contract and how many signers control it.
- Do not leave funds in wrapped form longer than the task requires.
- Test with a small amount before any large transfer, every time.
Key takeaways
- Bridges issue a representation on one chain against value held on another.
- Pooled collateral plus complex verification makes them prime targets.
- Wrapped tokens carry the bridge's risk, not just the asset's.
- For moving a balance between chains, a direct swap avoids the whole surface.
Cryptozilla lets you send on one network and receive on another in a single order — see the supported networks or read about choosing a USDT network.
Frequently asked questions
Is bridging safe?
It varies enormously by bridge. Canonical rollup bridges with on-chain verification are considerably safer than third-party multisig bridges. In every case you take on a risk that a direct swap does not require.
What is a wrapped token?
A token on one chain that represents an asset held on another, such as wrapped BTC on Ethereum. Its value depends on the collateral behind it remaining intact and redeemable.
Is a swap service better than a bridge?
For simply moving value between chains, usually yes: you receive the native asset rather than a wrapped claim, and you avoid contract approvals. Bridges remain necessary inside DeFi workflows that need a specific wrapped asset.
