USDT0 is a wrapped, omnichain version of Tether's USDT built on LayerZero's Omnichain Fungible Token (OFT) standard. It exists so USDT can move into chains where Tether has not deployed a native contract, without spinning up a separate canonical issuance for each new network. If you have ever held USDT on Arbitrum, Optimism, or a newer L2 and wondered why the contract address looked different from mainnet USDT, that is the gap USDT0 fills.
​

This guide walks through how USDT0 actually works, which chains it lives on, how it compares to native and bridged USDT, and where the real risks sit. Sources: layerzero.network documentation, usdt0.to, and DeFiLlama.
​

USDT0 is an OFT-standard token that represents USDT on chains that lack a Tether-issued native deployment. Each unit is backed one-to-one by USDT held in an Ethereum mainnet lockbox, and supply on every connected chain is reconciled through LayerZero messaging. The wrapper is run by Everdawn Labs in collaboration with Tether and LayerZero.
​

The point of USDT0 is to give USDT a single, fungible representation across many chains. Instead of each chain getting its own bridged variant from a different bridge operator, USDT0 routes everything through one canonical OFT contract per chain. Balances move by burning on the source chain and minting on the destination, not by holding separate liquidity pools per route.
​

OFT is a LayerZero token contract template. When you send USDT0 from chain A to chain B, the contract on A burns your tokens, LayerZero's messaging layer relays a verified message to chain B, and the contract on B mints the same amount to your address. The mainnet USDT collateral stays locked in a vault throughout — only the omnichain representation moves.
​

LayerZero's messaging relies on two independent parties: a Decentralized Verifier Network (DVN) that attests to the source-chain event, and an Executor that delivers the message on the destination chain. Token issuers configure which DVNs they trust. For USDT0, the configuration is documented at docs.usdt0.to; reviewing it is the first step if you are integrating the token in a protocol.
​

The practical upshot: there is no liquidity pool to drain, no LP tokens, and no per-route slippage. Fees are LayerZero messaging fees plus destination gas, paid in the source chain's native asset.
​

USDT0 launched on Ink in late 2024 and has expanded across additional EVM and non-EVM networks throughout 2025. The current live list includes Ethereum (as the lockbox chain), Arbitrum, Optimism, Ink, Berachain, Unichain, Hyperliquid, and additional rollups added over time. Because the deployment list changes, treat the official site as the source of truth rather than any third-party tracker.
​

Verify any specific chain at usdt0.to before sending funds. Contract addresses for each network are published in the USDT0 docs; copy them from there, not from a block explorer search, since lookalike contracts deployed by unrelated parties can appear in search results.
​

The three flavors of USDT look identical in a wallet but behave differently under the hood. Native USDT is a contract Tether deployed directly on a chain (Ethereum ERC20, Tron TRC20, Solana SPL, TON Jetton, BNB Chain BEP20, and others). Bridged USDT is a wrapper minted by a third-party bridge against locked native USDT on another chain. USDT0 is a Tether-affiliated OFT wrapper that uses LayerZero as its sole transport.

The cleanest mental model: native USDT is what Tether mints on a chain it supports directly. USDT0 is what Tether and LayerZero collaborate to mint on chains Tether has not deployed to. A bridged USDT from a random bridge is whatever that bridge decided to mint, with that bridge's security assumptions baked in.
​

Hold native USDT when the chain you are on has a Tether-issued contract — Ethereum, Tron, Solana, TON, BNB Chain, Polygon, Avalanche, and others all qualify. The trust surface is just Tether. Hold USDT0 when you need USDT exposure on a chain Tether has not deployed natively, such as Ink, Berachain, or Hyperliquid, and you accept the additional LayerZero messaging-layer assumption.
​

For most users the choice is made for them by the chain. If Tether is on the chain, you will receive native USDT from any reasonable on-ramp. If Tether is not on the chain, USDT0 is generally the canonical option supported by exchanges and front-ends. The decision worth making is whether to bridge into a USDT0 chain at all for large balances — sometimes parking funds on a native-USDT chain and bridging only when needed is the lower-risk path.
​

USDT0 inherits two trust assumptions: Tether's reserve solvency, same as any USDT, and LayerZero's messaging integrity. If a DVN configured by USDT0 is compromised and the security stack does not catch it, a malicious mint on a destination chain becomes possible. The mitigation is the multi-DVN configuration USDT0 documents — review it before committing meaningful capital.
​

Smart-contract risk applies to the OFT contracts on every chain, including the lockbox vault on Ethereum. Audits are linked from the USDT0 documentation. Operational risk also matters: if LayerZero's relayers or executors halt, transfers pause until they resume, even though no funds are at risk during the pause.
​

One specific footgun: USDT0 and native USDT on the same chain are different contract addresses and not interchangeable. Sending USDT0 to an exchange deposit address that only accepts native USDT will result in lost funds. Always confirm which token the destination accepts before sending.
​

The clearest use case is USDT exposure on chains Tether has not yet deployed to. New L2s and app-chains often launch without a Tether contract, and OFT-based USDT0 lets them bootstrap stablecoin liquidity without waiting for a native deployment. Hyperliquid, Ink, and Berachain all fall into this category at the time of writing.
​

The second use case is unified cross-chain accounting. Treasuries, market-making desks, and protocols that operate on multiple chains can hold USDT0 and move balances between chains through LayerZero messaging instead of routing through bridges with different security models. The omnichain representation simplifies reconciliation.
​

For end users, the practical pattern is: bridge in via the chain's official front-end, hold USDT0 while you transact onchain, and convert back to native USDT when you exit to an exchange or off-ramp. Most front-ends abstract the wrapping step entirely.
​

Circle's CCTP for USDC is the closest analog, but it works differently. CCTP burns USDC on the source chain and mints native USDC on the destination — there is no wrapper, just a single canonical USDC contract per chain coordinated through Circle's attestation service. USDT0 instead wraps mainnet USDT and uses LayerZero as the transport.
​

The trade-off: CCTP gives you native USDC at the destination, with Circle as the sole trust assumption. USDT0 gives you a wrapped representation backed by a mainnet lockbox, with both Tether and LayerZero in the trust path. Neither is strictly better — they reflect different choices by the issuers about how to scale a stablecoin across many chains.
​

For developers building cross-chain applications, the integration pattern differs too. CCTP exposes a burn-and-attest flow that protocols call directly. OFTs expose a send function on the token contract itself. Eco's intent-based routing handles both transports underneath a unified interface, so a sending application does not need to maintain separate bridge integrations per stablecoin.
​

Token mechanics and OFT standard details: LayerZero documentation at docs.layerzero.network. USDT0 specifics, supported chains, and contract addresses: usdt0.to and docs.usdt0.to. Live USDT supply figures: DeFiLlama stablecoins API, snapshot from May 2026. CCTP comparison: Circle CCTP documentation.
​

This article does not quote per-chain USDT0 supply figures because they shift weekly; check DeFiLlama or the USDT0 site for current numbers. Contract addresses change only when new chains launch — the official site is canonical.
​