CoinPayBank is an education site, not a bank. We don’t hold funds, take deposits or make loans. Not financial advice. Read disclaimer

Bridges Explained — and Why They Get Hacked

What a bank would do — and what you do instead

A bank runs your payments through card networks, ACH and wires, with business-day cut-offs, fees and the ability to dispute a charge. Stablecoin payments settle wallet to wallet in seconds, any day of the week, usually for small fees. In exchange, you take over the bank’s checks: confirming the recipient, choosing the right network, keeping records and accepting that most mistakes cannot be reversed.

How a bridge works

Blockchains cannot read each other directly. A bridge watches one chain, then tells the other chain what happened. In the common “lock and mint” model, your tokens are locked in a contract on chain A, and a wrapped copy is minted on chain B. Your wrapped copy is only as good as the bridge’s locked pool.

Main bridge types

TypeWho you trustExample use
Native / canonicalThe chains’ own protocol (e.g. an L2’s official bridge)Moving ETH to Base or Arbitrum
Issuer burn-and-mintThe token issuerSome stablecoins move this way natively across chains
Third-partyA validator set or multisig run by the bridgeMoving between unrelated chains

Why they get hacked

  • Huge pools of locked tokens sit in one contract.
  • Small validator sets or multisigs can be compromised.
  • Logic that verifies messages between chains is complex and easy to get subtly wrong.

Frequently asked questions

Is bridging the same as swapping?

No. A swap exchanges one token for another on the same chain. A bridge moves a token across chains.

Are official L2 bridges safer?

They generally rely on fewer extra parties, but they have their own design assumptions and withdrawal delays.

Last reviewed:

The Weekly Rate Report

One calm email a week: where stablecoin and staking yields moved, what changed in risk, and one thing to learn. No hype, no spam.

Unsubscribe anytime. We never sell your email.