Omnichain vs Wrapped vs Bridged Tokens: What's the Difference?

The multichain token problem

Blockchains do not natively talk to each other. A token issued on Ethereum has no idea that Solana, TON, or an Arbitrum rollup exists, and vice versa. Yet users expect to move "the same" asset wherever they want to trade, stake, or pay. To bridge that gap, the industry invented several different ways to make a token appear on a chain other than its home chain — and the label on the token often hides which mechanism is really underneath.

The catch is that these mechanisms are not interchangeable. Depending on how a token crossed chains, "USDC on chain B" or "ETH on chain B" can be a genuinely canonical asset, a custodian's IOU, or a bridge's receipt — each with different failure modes. Understanding the three dominant models — wrapped, bridged, and omnichain — is the difference between knowing what you actually hold and hoping it redeems one day.

Wrapped tokens: lock-and-mint

A wrapped token is a representation of an asset that is locked somewhere else. The classic pattern is lock-and-mint: you deposit the original asset with a custodian or a smart contract, and an equivalent "wrapped" token is minted for you on the destination chain. Wrapped Bitcoin (WBTC) is the canonical example — real BTC sits in custody, and an ERC-20 that tracks it circulates on Ethereum.

The value of a wrapped token is only as good as whatever holds the locked collateral. If a centralized custodian holds the reserves, you inherit counterparty risk: the wrapper is redeemable only while the custodian remains solvent, honest, and operational. If a smart contract or bridge holds the collateral instead, you inherit that contract's security. Either way, the wrapped token is a claim on assets you no longer directly control, and de-pegs happen precisely when the market doubts that the claim can be honored.

Bridged tokens: bridge-issued representations

Bridged tokens are close cousins of wrapped tokens, and the terms are often used loosely. In practice, "bridged" usually refers to a representation minted by a specific cross-chain bridge when you move an asset over. The original is locked (or burned) on the source chain, and the bridge issues its own version on the destination. If you want to learn the mechanics step by step, our guide on how to bridge crypto across chains walks through the flow.

Two problems follow. First, liquidity fragmentation: if three different bridges each mint their own "USDC" on the same chain, you end up with three non-fungible versions that do not automatically trade one-for-one. Users get stranded holding the wrong variant, and liquidity splinters across incompatible pools. Second, bridge-security risk: the bridge's lock contract becomes a concentrated honeypot, and several of the largest exploits in crypto history have drained exactly these contracts. When a bridge is compromised, the tokens it issued can become unbacked overnight.

Omnichain tokens (OFT / native): one canonical supply

The omnichain model attacks the root cause: instead of wrapping or re-issuing, it treats the token as a single asset with one canonical supply that simply moves between chains. LayerZero's Omnichain Fungible Token (OFT) standard is the best-known implementation. Rather than locking collateral and minting a wrapper, an OFT burns tokens on the source chain and mints the same amount on the destination, so the total supply across all chains stays constant and there is no separate wrapped copy to de-peg.

Because the movement is burn-and-mint on a token the issuer controls end to end, there is no third-party bridge honeypot holding your collateral, and no proliferation of incompatible variants — the token is the same asset everywhere it lands. If you want the deeper mechanics, see what is an OFT (Omnichain Fungible Token), and for the messaging layer that carries these transfers, what is LayerZero. As of 2026, the security assumption shifts from "trust a bridge's lock contract" to "trust the token contract and the underlying messaging protocol" — a smaller, more auditable surface, though not a zero-trust one.

Side-by-side: which is simplest and lowest-risk?

Wrapped tokens depend on a custodian or contract holding real collateral; your token is an IOU. Bridged tokens depend on a specific bridge that both holds collateral and issues a chain-specific variant, adding fragmentation on top of custody risk. Omnichain tokens keep one canonical supply and move it by burn-and-mint, removing both the wrapper and the fragmented copies.

For an everyday user, the omnichain model is usually the simplest mental model and the lowest-friction to hold: one asset, one balance, no "which version do I have?" guessing game and no locked-collateral honeypot as a single point of failure. It does not eliminate smart-contract or protocol risk — nothing does — but it removes two of the most common ways multichain tokens go wrong. The right choice still depends on the specific token, its issuer, and where you need to use it.

How WATS uses this

ATS, the token used across the WATS Hot Wallet, follows the omnichain model: it is a LayerZero OFT, so you hold a single ATS balance that works across EVM, Solana, and TON rather than wrapped or bridged copies you would have to reconcile. Inside the WATS Hot Wallet, every action is charged in ATS instead of each chain's native gas — on EVM via an ERC-4337 paymaster, and on Solana and TON via an equivalent fee-payer, with collected ATS burned from 100M toward a 30M floor. WATS is non-custodial: you hold your own keys, and you can read more about the fee mechanism on the ATS fee page.