The two mental models · burn-and-mint vs lock-and-wrap
Cross-chain bridges work in one of two ways. The mechanism matters because the security profile differs.
Burn-and-mint (native)
The bridge burns the original token on the source chain (the supply on chain A is reduced) and mints a new token on the destination chain (the supply on chain B is increased). The token on chain B is the native, issuer-authorised version. Circle's CCTP uses this model. The security profile is the strongest because there is no wrapped-token contract holding a pool of value that can be exploited. The trade-off is that the bridge requires cooperation from the token issuer; not every stablecoin can be moved this way.
Lock-and-wrap
The bridge locks the original token in a contract on chain A and mints a "wrapped" version on chain B. The wrapped token represents a claim on the locked token. Most pre-2024 bridges used this model. The locked pool is the value at risk; the historical bridge exploits — Wormhole, Ronin, Nomad, Multichain — all hit lock-and-wrap contracts. The model still works for tokens whose issuer does not support native cross-chain, but the security profile is structurally weaker.
Bridge 01 · Circle CCTP
Circle Cross-Chain Transfer Protocol (CCTP)
Circle launched CCTP in April 2023, six weeks after the SVB depeg, partly to reduce the wrapped-USDC contagion risk that had bitten DeFi during the depeg. The protocol works by burning native USDC on the source chain via Circle's Token Messenger contract, sending an attestation through Circle's off-chain message service, and minting native USDC on the destination chain via the Token Messenger contract there.
Supported chains (mid-2026). Ethereum, Solana, Base, Arbitrum, Optimism, Avalanche, Polygon, Noble (the Cosmos USDC chain). Sui and Aptos support landed in 2025. BNB Chain is not natively supported as of mid-2026 (USDC on BNB Chain is still the wrapped version).
The trap. CCTP's attestation requires a finality wait on the source chain. For Ethereum mainnet, that is 12-15 minutes (the recently-introduced "Fast Transfer" mode reduces this for some pairs but adds a 0.01-0.04% fee). For Solana, finality is much faster but the destination chain might be Ethereum, which adds the wait back at the other end. Plan for 13-19 minutes start to finish as a working baseline.
When to use. Any cross-chain USDC transfer where the source and destination chains are both supported. The structurally safest option. The fee is small enough that for amounts above 200-300 USD, CCTP usually beats the alternatives on combined fee + risk.
[00:00] Approve Token Messenger contract on Ethereum, gas 0.0024 ETH (~8 USD).
[00:01] Send 1,500 USDC, gas 0.0031 ETH (~10 USD).
[00:14] Attestation appears in Circle's API.
[00:15] Receive 1,500 USDC on Base, gas 0.00003 ETH (~0.10 USD).
Total time: 15 minutes. Total cost: 18.10 USD (mostly Ethereum gas). USDC received: 1,500 (no Circle fee on standard transfer in 2026).
Bridge 02 · Stargate Finance
Stargate Finance
Stargate is the largest LayerZero-based cross-chain bridge, built on the "unified liquidity pool" model. Each supported token sits in a pool on each supported chain. A transfer takes from one pool and gives to another, with LayerZero providing the cross-chain messaging. The pools are funded by liquidity providers earning fees.
Supported chains (mid-2026). Ethereum, Arbitrum, Optimism, Base, Polygon, Avalanche, BNB Chain, Linea, Scroll, Mantle, Metis, Aurora, plus a handful of smaller L2s.
The trap. Pool imbalance. If the destination chain's pool for your token is low, the bridge either holds your transfer until the pool is rebalanced, or routes through a different intermediate token (USDC → ETH → USDC, for example), adding slippage. Stargate's UI usually warns about this but first-time users miss the warning. Check the pool depth on the source-and-destination pair before sending.
When to use. USDT transfers (CCTP does not support USDT). Cross-chain transfers among Ethereum L2s where Stargate's fast-path route is competitive on speed. Larger transfers where the small percentage fee is fine and the user wants a single transaction rather than CEX deposit-and-withdraw.
[00:00] Approve Stargate router on Arbitrum, gas ~0.20 USD.
[00:01] Send 1,000 USDT, gas ~0.35 USD + Stargate fee 0.06 USDT.
[00:02] LayerZero message processed.
[00:03] Receive 999.94 USDT on Optimism, gas absorbed by Stargate.
Total time: 3 minutes. Total cost: 0.61 USD. USDT received: 999.94 (Stargate fee 0.006%).
Bridge 03 · Allbridge
Allbridge Core
Allbridge runs its own validator set for cross-chain messaging plus a liquidity pool on each supported chain. The model sits between Stargate (LayerZero messaging) and CCTP (native burn-and-mint). Useful as a USDT bridge for chains where Stargate has thin liquidity.
Supported chains (mid-2026). Ethereum, BNB Chain, Polygon, Avalanche, Solana, Arbitrum, Tron (partial — Tron support is for specific tokens), TON, Sui, Stellar.
The trap. Less liquidity than Stargate on most pairs. Allbridge's bridge fee is competitive but the slippage on larger transfers can be noticeable. For amounts above 5,000 USD, check the quoted output and compare against Stargate's quote before sending.
When to use. USDT or USDC transfers to chains that Stargate does not support natively (Sui, Stellar, TON). USDT transfers when Stargate's pool on the destination chain is imbalanced.
[00:00] Approve Allbridge router on Polygon, gas ~0.02 USD.
[00:01] Send 500 USDC, gas ~0.03 USD + Allbridge fee 0.95 USDC.
[00:04] Allbridge validators sign the transfer.
[00:05] Receive 499.05 USDC on Solana, gas absorbed by Allbridge.
Total time: 5 minutes. Total cost: 0.05 USD + 0.95 USDC fee. USDC received: 499.05 (Allbridge fee 0.19%).
Bridge 04 · LayerZero-routed aggregators (Jumper, deBridge, Across)
Aggregators · Jumper, deBridge, Across Protocol
Aggregators do not run their own bridge; they route your transfer through whichever underlying bridge offers the best quote at the moment. Jumper Exchange (built by LiFi) is the most-used in 2026. deBridge and Across Protocol have similar functionality with different routing algorithms. The UX is the cleanest among the options — paste an amount, source chain, destination chain and recipient, and the aggregator routes through whatever combination is cheapest.
The trap. Route opacity. The aggregator picks the cheapest route but the chosen route is sometimes a wrapped-token bridge with weaker security than CCTP. Expand the route details before confirming if you care about the underlying mechanism. For amounts above 1,000 USD where security matters more than the marginal fee saving, prefer the direct CCTP route if both ends are supported.
When to use. Small or one-off transfers where convenience matters more than the marginal fee or security difference. Routes that involve a chain unsupported by CCTP or Stargate.
The exchange route (often the right answer)
For users with a Binance, OKX, Bybit, KuCoin or Kraken account, the cheapest and fastest route is frequently the centralised exchange: deposit on chain A, withdraw on chain B. The exchange handles the chain swap internally using its own liquidity pools.
Exchange deposit-and-withdraw
Deposit USDT-ERC-20 on Binance. Wait for confirmation (12 Ethereum blocks for Binance, roughly 3 minutes). Withdraw as USDT-TRC-20. Receive on Tron in roughly 1 minute. Total time: 5-10 minutes. Total fee: 1 USDT (Binance TRC-20 withdrawal fee in 2026).
The trap. Custody risk during transit. Your funds sit on the exchange between deposit and withdrawal. For amounts above a few thousand USD and for users with strong self-custody preferences, the brief custody exposure may be unwelcome. For most retail users, the exchange route is the cheapest and fastest option in 2026.
When to use. Chain pairs the exchange supports natively. Amounts below the threshold where custody risk is material. Conversions to chains that bridges do not support (USDT to Tron is exchange-only because Tether issues USDT-TRC-20 directly rather than bridging).
[00:00] Send USDT-ERC-20 from MetaMask to Binance deposit address. Gas ~5 USD.
[00:03] 12 Ethereum confirmations, balance credited on Binance.
[00:04] Initiate USDT-TRC-20 withdrawal to Trust Wallet Tron address.
[00:06] Withdrawal processed by Binance.
[00:07] Receive 499 USDT-TRC-20 in Trust Wallet (500 - 1 USDT Binance withdrawal fee).
Total time: 7 minutes. Total cost: 5 USD (Ethereum gas) + 1 USDT (Binance fee). USDT received: 499.
What route the desk uses · pattern by destination
- USDC, Ethereum → Base. CCTP. Cheaper and structurally safer than alternatives.
- USDC, Ethereum → Solana. CCTP. Same reasoning.
- USDC, Ethereum → BNB Chain. Stargate or exchange. CCTP does not support BNB Chain natively. The wrapped USDC on BNB Chain is functional but the security profile is worse; if the use case requires native USDC on BNB Chain, the exchange route is usually best.
- USDT, Ethereum → Tron. Exchange. No on-chain bridge issues native USDT on Tron because Tether mints it directly.
- USDT, Arbitrum → Optimism. Stargate fast-path. 3 minutes, sub-dollar all-in cost.
- USDT, BNB Chain → Polygon. Stargate. Allbridge as a backup if Stargate pool is imbalanced.
- USDC, anywhere → Sui or TON. Allbridge. Limited alternative for these chains.
The exploits to remember
Five operational tips
- Use a test transfer first. For any new chain or new bridge, send a small amount (10-20 USDC or USDT) and confirm the destination receives correctly before sending the full amount. The 20 USD of friction is the cheapest insurance in crypto operations.
- Check the receiving chain has gas. The bridge delivers the stablecoin but not the native gas token. Sending USDC to a fresh Solana wallet means you have USDC but no SOL to pay gas to do anything with it. Some bridges include a small native-token transfer as part of the bridge transaction; check the option before sending.
- Approve only the amount you are sending. Bridge router contracts ask for token approvals. The convenient option is "unlimited" — but a compromised router contract can drain any approved balance. Use "exact amount" approvals for stablecoin bridges; revoke old approvals periodically via Revoke.cash or similar.
- Confirm the recipient address chain. A USDC-on-Solana address looks completely different from a USDC-on-Ethereum address. Mixing them is a common loss vector. Most wallets in 2026 detect chain mismatches but do not rely on the wallet; visually confirm the chain on both sides.
- Save the transaction hash. If a bridge stalls or appears to fail, the source-chain transaction hash is the only artifact that lets you trace the transfer. Save it before navigating away from the bridge UI.
If you want to act on this
For users whose primary venue is Binance, the exchange's deposit-and-withdraw route is frequently faster and cheaper than any on-chain bridge for the common chain pairs. The referral link opens a Binance registration page pre-filled with code BN16188; registering through that link does not change your fees. Full disclosure on the disclaimer page. For self-custody users, Circle's CCTP for USDC and Stargate for USDT remain the working defaults; the desk uses both regularly.
Bridge documentation we lean on
- Circle CCTP documentation, circle.com/cross-chain-transfer-protocol.
- Stargate Finance documentation, stargate.finance.
- Allbridge Core documentation, core.allbridge.io.
- LayerZero protocol whitepaper and audit reports.
- Chainalysis cross-chain bridge incident reports, 2022-2024.
- Rekt News bridge exploit reconstructions (Wormhole, Ronin, Nomad, Multichain, Orbit).
Further reading on this site
- USDT vs USDC, the 2026 report — for the broader question of which token to hold on which chain.
- How to choose your first stablecoin — for the on-ramp companion piece.
- How to cash out stablecoins — for the off-ramp companion piece.
- Glossary — definitions for CCTP, LayerZero, finality, attestation, validator-set.