DeFi

Crypto Bridges: What You Are Actually Trusting When You Cross Chains

By Thomas Lovas Lokoy — researched and drafted with AI from published sources; edited and published by NorwegianSpark SA | Last updated: 2026-10-16

This article contains affiliate links. We may earn a commission at no extra cost to you. Full disclosure

Not financial advice. Crypto assets carry risk and on-chain transactions are irreversible. Do your own research.

Move an asset from one chain to another and the interface says it was transferred. Nothing was transferred. Blockchains cannot see each other, and no token has ever crossed between them.

What happened is that your asset was immobilised on the first chain and a representation of it was created on the second. Understanding that sentence is the whole of bridge risk, because the thing holding the immobilised asset is now the thing you are trusting.

The mechanism

Bridges vary in design, but the common pattern is the same shape.

You send your asset to a contract or a custodian on the origin chain, which locks it. On the destination chain, a corresponding token is issued to you. That token is not the original asset. It is a claim on the original asset, honoured by whatever is holding it.

To go back, the destination token is destroyed and the original is released.

The consequence is that the wrapped token you now hold is only worth the original for as long as the lock-up remains intact and the issuer keeps honouring the claim. Break either and the wrapped token is a claim on nothing — which is exactly what has happened, more than once, when a bridge's holdings were drained while the wrapped tokens continued to exist on the other side.

Trusted and trustless, and why the distinction matters

Ethereum.org divides bridges into two categories, and its descriptions are worth quoting rather than paraphrasing (ethereum.org/bridges).

Trusted bridges "depend upon a central entity or system for their operations". They have "trust assumptions with respect to the custody of funds and the security of the bridge", users "mostly rely on the bridge operator's reputation", and users "need to give up control of their crypto assets".

Trustless bridges "operate using smart contracts and algorithms", so "the security of the bridge is the same as that of the underlying blockchain", and they "enable users to remain in control of their funds".

Put more sharply: a trusted bridge asks you to believe in an operator. A trustless one asks you to believe in code. Neither is a guarantee, and the second is not automatically safer — code with a bug is not safer than an operator with a reputation. It is a different failure mode, and knowing which one you are exposed to is the point of the distinction.

The risks, as the documentation itself lists them

The same page is direct about this, and it applies to every bridge regardless of design.

  • Smart contract risk — "the risk of a bug in the code that can cause user funds to be lost".
  • Technology risk — "software failure, buggy code, human error, spam, and malicious attacks can possibly disrupt user operations".

Trusted bridges add two more on top:

  • Censorship risk — operators "can theoretically stop users from transferring their assets using the bridge".
  • Custodial risk — the operator is holding your assets.

And the framing the page opens that section with deserves repeating: "Bridges are in the early stages of development. It is likely that the optimal bridge design has not yet been discovered."

That is official Ethereum documentation describing the state of the art as unfinished. It is a more honest risk statement than most bridge interfaces put in front of users.

Why bridges concentrate risk

A bridge holds the locked assets for everyone who has ever crossed it. That makes it a single contract or custodian holding a very large balance, permanently, in public, with an address anyone can look up.

Three properties compound.

The value is pooled. Individual wallets each hold their own; a bridge holds everybody's.

The code is complex. A bridge has to verify events on one chain from another, which is a genuinely hard problem, and complexity is where bugs live.

The failure is total for those exposed. When the lock-up is drained, every wrapped token on the destination side is affected at once, whether or not its holder was doing anything at the time.

None of this makes bridging wrong. It makes it a decision that deserves a moment's thought rather than a reflex, and it makes leaving assets in wrapped form indefinitely a worse idea than most people treat it as.

Worked example (illustrative figures). You bridge 5,000 USDC to another chain and receive 5,000 of a wrapped version. If the lock-up behind it is drained and the wrapped token falls to 0.10 on the destination chain, your position is worth 5,000 x 0.10 = 500. If you had crossed for one afternoon to use an app and then moved into a native asset, the window in which that could happen to you would have been hours rather than months. Time held in wrapped form is the variable you control.

The canonical bridges of optimistic rollups show the trade-off from the other side. Withdrawals back to Ethereum wait out a challenge period, 6.4 days on Arbitrum (Arbitrum docs) and 7 days on OP Stack chains (Optimism docs), so that an invalid withdrawal can be challenged. Fast third-party bridges skip the wait for a fee by adding their own operator and contracts to what you trust; our Ethereum layer 2 guide works through that choice.

Reducing the exposure

  • Bridge for a purpose, not as storage. Cross for a specific reason, do the thing, and come back or move into a native asset. Time exposed is the variable you control.
  • Prefer a native asset on the destination chain where one exists. If a chain has a native, canonical version of what you want, using it removes the bridge from your risk entirely.
  • Prefer bridges operated by the chain itself where the option exists, since a chain's own canonical bridge is usually the most scrutinised path in and out of it.
  • Do not chase yield across bridges. A return that requires bridging into an unfamiliar wrapped asset is compensating you for exactly this risk, and the compensation is rarely proportionate. Our piece on crypto yield and where it comes from covers how to read those offers.
  • Test small, always. A small test transfer costs a fee and catches wrong-chain, wrong-address and unsupported-asset errors before they are expensive.

Frequently Asked Questions

Is a wrapped token the same as the real asset?

No. It is a claim on an asset held elsewhere, honoured by whatever holds it. It usually trades at parity because the claim is expected to be good, and it stops trading at parity the moment that expectation is questioned.

Are trustless bridges safe?

Safer against custodial and censorship risk, since no operator holds your assets. They remain fully exposed to smart contract risk and technology risk, which the Ethereum documentation lists for every bridge type. Trustless means the trust moved from an operator to code, not that it disappeared.

What happens to my wrapped tokens if a bridge is drained?

They continue to exist on the destination chain and lose their backing, because the assets that were supposed to redeem them are gone. Whether anything is recovered depends on the operator, any insurance arrangement, and what the community decides — none of which is a right you hold.

Can I avoid bridges completely?

Often, yes. Buying the native asset on the destination chain through an exchange, and withdrawing it directly to that chain, achieves the same end position without a bridge, and substitutes exchange risk for bridge risk. Which is preferable depends on amount, duration and what you are doing.

The one sentence to keep

Bridging does not move your asset — it locks it somewhere and gives you a claim, and every bridge risk is a variation on that claim not being honoured.

Treat wrapped assets as temporary, test with small amounts, know whether an operator or a contract is holding the other side, and the mechanism stops being mysterious.

Sources: the Ethereum bridges documentation (ethereum.org), read 19 August 2026; Arbitrum and Optimism withdrawal documentation, read 16 October 2026. No third-party bridge is recommended and no incident figure is quoted here; the worked example is illustrative.

Sources

Thomas Lovas Lokoy · Founder & Editor, NorwegianSpark SA

Thomas Lovas Lokoy is the founder of NorwegianSpark SA, the Norwegian company (org. 834 984 172) that runs AICryptoCoin. He oversees the business. Articles are researched and drafted with AI assistance; Thomas is responsible for what goes live. Corrections: thomaslien@norwegianspark.com.

Editorial policy · Affiliate disclosure

Content on AICryptoCoin is for informational purposes only and does not constitute financial advice. Always do your own research and consult a qualified financial advisor before making investment decisions.

Continue in this collection