Bridging

Definition

Bridges transfer value across blockchains. They are historically high-risk attack surfaces; researchers treat bridge TVL and security assumptions carefully, especially when an L2 or multi-chain thesis depends on them.

Bridge designs differ: trusted multisigs, light clients, optimistic proofs, intent-based routers. Your risk note should name the trust model, not only the brand on the UI button. Composability imports risk from oracles and collateral you did not write.

Withdrawal delays, custody of locked assets, and oracle assumptions matter as much as throughput marketing. Fast bridges sometimes buy speed with trust tradeoffs. Burn accounting differs by dashboard — reconcile before dilution math.

For L2 and multi-chain apps, bridging is part of user experience and part of systemic risk. Liquidity that exists only as bridged representation can vanish or depeg when the bridge fails.

Why researchers care

• Bridge exploits have caused some of crypto’s largest losses.
• Withdrawal delays and custody models vary by design.
• L2 research must include bridge risk.
• Bridged liquidity is not identical to native liquidity.

How to use it in research

• An L2 TVL mostly sitting in a canonical bridge — document upgrade keys and delay windows.
• A “fast bridge” using third-party liquidity — separate third-party credit risk from base-chain security.
• Wrapped assets trading below nav after bridge uncertainty — treat as depeg risk in the thesis.

Common mistakes

• Assuming bridges inherit full L1 security automatically.
• Ignoring exit delays when sizing short-horizon trades.
• Counting bridged TVL as risk-free protocol demand.