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

Wrapped, bridged and omnichain tokens are three different ways to make one asset usable on more than one chain, and the difference is what you are actually holding. A wrapped token is minted on the destination chain against collateral locked with a custodian or a contract elsewhere, so it is a claim that is only ever as good as its backing; a bridged token is that same lock-and-mint idea issued by one particular bridge, which is why a single chain can end up with several versions of the same asset that are not fungible with each other. An omnichain token — most commonly LayerZero's OFT standard — has no wrapper at all: it is burned on the source chain and minted on the destination, so one canonical supply moves between chains instead of duplicating. That distinction matters in practice, because the omnichain model removes both the locked-collateral honeypot and the which-version-do-I-have problem, while wrapped and bridged tokens add custody risk and liquidity fragmentation on top of the transfer itself. ATS, the fee token in the non-custodial WATS wallet, is a LayerZero OFT for exactly this reason: one ATS balance pays network fees across the chains WATS supports rather than splitting into wrapped copies.

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 close that gap, the industry invented several different ways to make a token appear on a chain other than its home chain — and the ticker on your balance usually hides which mechanism is really underneath.

The mechanisms are not interchangeable. Depending on how it crossed chains, "USDC on chain B" or "ETH on chain B" can be a natively issued asset, a custodian's IOU, or one bridge's receipt — each with a different failure mode. Understanding the three dominant models — wrapped, bridged, and omnichain — is the difference between knowing what you 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: the original asset is deposited 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 textbook example — 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 centralised custodian holds the reserves, you inherit counterparty risk: the wrapper is redeemable only while that custodian remains solvent, honest and operational. If a smart contract holds the collateral instead, you inherit that contract's security and its upgrade keys. Either way the wrapped token is a claim on assets you no longer directly control, and de-pegs happen precisely when the market starts to doubt that the claim can be honoured. A wrapper also has to be unwrapped through the same route to get the original back, which matters if that route is ever paused.

Bridged tokens: one bridge's representation

Bridged tokens are close cousins of wrapped tokens, and the two words are often used loosely. In practice "bridged" usually means 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 that bridge issues its own version on the destination. If you want the mechanics step by step, the guide on how to bridge crypto across chains walks through the flow.

Two problems follow. First, liquidity fragmentation: if three bridges each mint their own version of USDC on the same chain, you end up with three tokens that share a ticker but are not fungible with one another and do not automatically trade one-for-one. Users get stranded holding the variant a given app or pool does not accept, and liquidity splinters across incompatible pools. Second, bridge-security risk: the lock contract becomes a concentrated honeypot, and several of the largest exploits in crypto history drained exactly these contracts. When a bridge is compromised, the tokens it issued can become unbacked overnight while the original asset on the home chain is untouched.

Not all bridged tokens are equal. A chain's canonical bridge — the one run by the rollup or network itself — usually issues the version that ecosystem apps treat as standard, which reduces the fragmentation problem but not the locked-collateral one. Separately, some issuers now mint natively on each chain and move supply by burn-and-mint rather than by wrapping, which is why you sometimes see a native token and an older bridged variant of the same asset living side by side on one network.

Omnichain tokens (OFT): 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 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 combined supply across all chains stays constant and there is no separate wrapped copy that can de-peg from it.

Because the movement is burn-and-mint on a token the issuer controls end to end, there is no third-party bridge sitting on your collateral and no proliferation of incompatible variants — the token is the same asset everywhere it lands. There is one common variation worth knowing: when a token already exists on a chain and cannot be redeployed, an OFT adapter locks the existing supply on that home chain and the OFT contracts on other chains mint against it, so the total in circulation is still fixed. For the deeper mechanics see what is an OFT (Omnichain Fungible Token), and for the messaging layer that carries these transfers, what is LayerZero. The security assumption shifts from "trust a bridge's lock contract" to "trust the token contract and the messaging protocol it is configured with" — a smaller and more auditable surface, though not a zero-trust one.

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

Model	How it reaches the other chain	What you hold	Main failure mode
Wrapped	Original locked with a custodian or contract, wrapper minted on the destination	A redeemable claim on collateral held elsewhere	Custodian insolvency or contract exploit breaks the backing and the wrapper de-pegs
Bridged	Locked or burned on the source, that specific bridge mints its own version	One bridge's variant of the asset, not necessarily fungible with the others	Bridge exploit leaves the variant unbacked; multiple variants fragment liquidity
Omnichain (OFT)	Burned on the source and minted on the destination by the token itself	The same canonical token, one supply across all chains	A flaw in the token contract or in the messaging layer it is configured with

Read down the last column and the ranking is clear enough. Wrapped tokens depend on someone holding real collateral. 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 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 guessing which version you have 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 to tell which one you are holding

• Check the contract address, not the ticker. Two tokens on the same chain can share a name and symbol and still be different contracts. The issuer's own documentation is the only authority on which address is canonical.
• Read the suffix. Names carrying a bridge marker, an extra letter, or a "wrapped" or "bridged" label are usually the derivative version rather than the native one.
• Look at who mints. On a block explorer, supply minted by a bridge contract signals a bridged representation; supply minted by the token contract itself on each chain is the omnichain or native pattern.
• Ask what happens if the route stops. If your token can only be redeemed through one bridge or custodian, that route is your real counterparty, whatever the ticker says.

How WATS uses the omnichain model

ATS, the token used across the WATS wallet, follows the omnichain model: it is a LayerZero OFT, so you hold a single ATS balance across the chains WATS supports — Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Solana and TON — rather than wrapped or bridged copies you would have to reconcile chain by chain. Inside the WATS Hot Wallet, network fees are charged in ATS instead of each chain's native gas token, on EVM chains through an ERC-4337 paymaster, with collected ATS burned as supply moves from 100M down to a 30M floor. That is not a discount: it changes which token pays the fee, not what the network charges. WATS is fully non-custodial throughout — the user holds the keys and WATS never holds one — and the mechanism is documented on the ATS fee page.

If you want to see the difference between these models in daily use rather than in theory, WATS is a straightforward place to observe it: keep one ATS balance, pay fees with it on all eight supported chains, and note that you never have to ask which wrapped variant of your fee token a given network expects. That single-balance behaviour is the practical payoff of the omnichain design described above, and it is the reason to prefer omnichain assets wherever the issuer offers one.