Bridge Without Friction

The moment it clicked for me was small and almost embarrassing: a bridge doesn't move your tokens. It locks them on one chain and issues a new representation on another, and the only thing that "travels" is a message. Once that lands, the rest of the puzzle stops being a black box and starts being plumbing you can reason about. Most failed first attempts happen because people skip this step and assume atomicity that the architecture never promised.

The two big families split on how that cross-chain message is produced. Liquidity-based bridges route through a pool: you deposit USDC on Ethereum, a market maker or vault releases USDC on Solana, and a fee comes out of the spread or a relayer. Useful when both chains have deep inventory, expensive when they don't. Burn-and-mint bridges, the kind you see for native assets, actually destroy the token on the source chain and mint on the destination. The supply is constant across both, which is the point, but it puts a heavy trust weight on the validator set or multisig doing the signing — typically a 2/3 quorum out of a known set.

The detail that catches first-timers is settlement. A swap on a single chain confirms in roughly 12 to 15 seconds, or ~12 seconds on Ethereum, and you can build on top of it immediately. A bridge adds another layer of confirmation on top of the receiving chain, plus a finality window for the outgoing transaction. The honest expectation is minutes, not seconds, and that window is where reorg risk and validator liveness live. The pragmatic version: if the destination is an L2 with its own challenge period, double it.

For amounts where you care about getting from A to B and don't care about the route, a Crypto Bridge aggregator handles the routing and the slippage math, which is the part a hand-rolled attempt usually gets wrong. Past that, the question of which bridge to trust for which asset is a different post, and the answer changes with every exploit.