For readers who already know stablecoins, USDT0 sits one layer above native USDT issuance and targets liquidity fragmentation across many USDT contract versions. As of late September 2026, Tether (USDT) market capitalization was about $183 billion (CoinMarketCap). USDT0 itself has grown to roughly $4.1 billion in circulation with cumulative transfer volume above $100 billion across about two dozen native deployments, plus Legacy Mesh routes for large legacy USDT footprints such as Tron and TON (The Block; USDT0 docs).
On January 16, 2025, Tether introduced USDT0 on Kraken’s Ethereum Layer 2 network Ink, using LayerZero’s Omnichain Fungible Token (OFT) standard. The launch goal was a shared cross-chain liquidity layer for USDT rather than another isolated wrapped stablecoin per chain.
Native USDT remains the largest stablecoin by market capitalization, but contract versions and bridge wrappers still fragment liquidity and raise transfer friction. USDT0 addresses that by keeping a single lock-and-mint relationship to Ethereum USDT while OFT messaging moves balances between connected chains.

Source: https://mirror.xyz/tetherzero.eth/4z1kh9wE6h07zGjrKImx4Cr-VIzCpRle0VElalG0Rss
Since its 2014 launch, Tether (USDT) has become the most widely used dollar-pegged crypto dollar. As of late September 2026, USDT market capitalization was about $183 billion (CoinMarketCap), with reserves described as primarily cash and cash equivalents, including short-term U.S. Treasuries. Cantor Fitzgerald has been associated with managing Tether’s U.S. Treasury holdings; Howard Lutnick, Cantor Fitzgerald’s CEO, later served as U.S. Secretary of Commerce—an institutional context note, not a USDT0 product claim.
Multi-chain growth left users with many USDT implementations, inconsistent upgrade paths, and bridge-dependent transfers. USDT0 is the omnichain layer designed to make those balances interoperable under one OFT-based supply model. For a side-by-side product framing, see Gate Learn’s USDT0 vs USDT explainer.

Source: https://coinmarketcap.com/currencies/tether
USDT0 reduces fragmentation by locking USDT in an OFT Adapter on Ethereum and minting an equal amount of USDT0 across destination blockchain networks. Users can send USDT0 between supported chains through LayerZero messaging and receive it on the other side, then redeem back to Ethereum USDT at 1:1 by burning USDT0 and unlocking the reserved USDT.
Typical flow:
Asset locking: USDT is locked in the Ethereum OFT Adapter (or a dedicated lockbox route for specific chains such as IOTA L1).
Minting on the target chain: After verification, an equal amount of USDT0 is minted on the destination network to the recipient address.
Omnichain transfers: LayerZero messaging sends a cross-chain message between networks before burn-and-mint completes, without requiring a separate AMM bridge pool for each hop.
Redemption: Burning USDT0 unlocks the matching USDT on Ethereum, preserving the 1:1 backing relationship.
Early Ink integration also allowed Kraken account flows for Ink-network USDT0. Ink founder Andrew Koller described the launch as setting a new liquidity standard for stablecoins on that L2—useful historical context for the first venue, not a guarantee of future venue coverage.

Source: https://docs.usdt0.to/overview/how-usdt0-works
USDT0 uses LayerZero’s OFT standard so the same logical token can expand to new chains while remaining backed by locked Ethereum USDT. Key design points:
| OFT property | What it means for USDT0 |
|---|---|
| Unified liquidity | One lock source on Ethereum instead of many wrapped USDT silos |
| Messaging security | Cross-chain actions verified via LayerZero’s oracle/relayer (DVN) model, with DVN settings configured per deployment; if misconfigured, verification risk can include fraudulent mints |
| Scalability | New chains can be added without spawning a separate wrapped ticker per bridge |
| Efficiency | Burn-and-mint removes the need to seed a bridge LP for every route |
Live native coverage should always be checked on the USDT0 deployments page. Documentation has listed on the order of 20+ native networks (for example Ink, Arbitrum, Polygon, Optimism, Berachain, Plasma, Mantle, MegaETH, HyperEVM, and others) plus Legacy Mesh endpoints—counts change as networks are added or wound down.
Source: https://docs.layerzero.network/v2/home/token-standards/oft-standard
Legacy Mesh is the interoperability layer that connects large legacy USDT deployments—historically including Ethereum, Tron, TON, and Arbitrum routes—into the USDT0 network with liquidity pools and LayerZero messaging. It launched on February 12, 2025, and is designed so a large share of global USDT supply can reach USDT0 rails without waiting for every chain to become a native OFT deployment.
How to use the public transfer UI:
Open usdt0.to/transfer.
Select source and destination chains for USDT or USDT0 from the table or list shown in the interface.
Use the UI to set route options for single-hop or multi-hop transfers when available (for example Tron → TON, or routes that touch Arbitrum/Ink).
Source: https://mirror.xyz/tetherzero.eth/NUSP9nxicfUulDFjEyXRC3LHUtL2c23fxRdE_3M79Es
USDT0’s first public deployment focused on Ink to pair OFT issuance with Kraken’s L2 liquidity and deposit/withdrawal UX. Andrew Koller stated that USDT0 combined with Ink was intended to give users and developers stronger asset control and a clearer liquidity standard on that network.
Reasons commonly cited for the Ink pilot:
Exchange distribution: Kraken users could deposit and withdraw USDT0 on Ink without assembling a separate bridge stack first.
L2 fee profile: Rollup-style fees are typically lower than Ethereum mainnet for frequent stablecoin moves.
Pilot security surface: A single L2 launch let teams stress-test OFT issuance, redemption, and exchange ops before broader expansion.
Interoperability path: Once live on Ink, USDT0 could extend to other OFT destinations while keeping Ethereum USDT as the lock source.
Expansion after Ink is no longer “planned only”: native deployments later included Arbitrum, Berachain, MegaETH, and many additional networks listed in official docs. Always confirm contract addresses on the deployments page before sending funds.
Source: https://blog.kraken.com/news/announcing-ink
USDT0’s cost thesis versus classic bridges:
Fewer bridge LP fees: OFT burn-and-mint avoids paying a separate liquidity provider on every route.
Leaner on-chain steps: LayerZero’s messaging path is designed to reduce the multi-step lock/verify/mint choreography of older bridges, which can lower gas vs multi-contract bridge flows (actual fees still depend on each chain’s gas market).
Less slippage from thin bridge pools: 1:1 mint/burn across supported chains does not rely on an AMM curve for the base conversion.
Tighter cross-chain price gaps: A shared issuance model reduces the room for large USDT price dislocations caused by uneven bridge inventory—though local DEX markets can still trade at short-lived premiums or discounts.
In short, OFT messaging plus 1:1 redemption aims to cut bridge markup, pool slippage, and inventory fragmentation—not to make every destination chain’s gas free.
USDT0’s main technical advantages relative to wrapped-bridge USDT are:
Burn-and-mint supply control: Source burn and destination mint keep total USDT0 aligned with locked Ethereum USDT, avoiding double-spend style inventory mistakes common in poorly designed bridges.
LayerZero messaging: Cross-chain packets are verified through LayerZero’s security stack rather than a single custodial bridge operator holding pooled inventory.
Upgradeable contract design: USDT0 contracts are structured for upgrades so logic can stay aligned across deployments as standards evolve.
Broad destination coverage: Native OFT deployments and Legacy Mesh together cover many high-liquidity venues; coverage is defined by docs, not by assuming every L1/L2 automatically supports USDT0.
The USDT0 Network documentation also places sibling omnichain products (such as XAUT0 for Tether Gold and USAT on selected chains) under the same lock-and-mint family—useful context that USDT0 is a network pattern, not a one-off ticker.
USDT0 focuses on four practical outcomes:
Native USDT historically lived as separate contracts per chain. Moving value often meant bridge wraps, custom routers, or CEX withdrawals. USDT0 packages that movement as OFT transfers against one Ethereum lock inventory.
Supported transfers target 1:1 amounts without an extra wrap/unwrap token layer. That design is especially relevant for desks, market makers, and protocols that operate across multiple chains with a standardized token path while rebalancing inventory across L2s frequently.
Many historical bridge losses came from pooled liquidity and weak verification. USDT0 still depends on messaging security and smart contracts, but it does not require users to trust a third-party AMM inventory for the base USDT↔USDT0 conversion.
Developers can treat USDT0 like a standard fungible token on each blockchain while relying on OFT for interoperability. Exchange listings, DeFi venues, and payment chains (for example payment-focused networks that later added USDT0) extend utility beyond the Ink pilot.
Source: https://usdt0.to/
| Dimension | Traditional multi-chain USDT | USDT0 |
|---|---|---|
| Supply model | Separate contracts / wrappers per chain | Ethereum lock + OFT mint/burn |
| Cross-chain path | Bridges, CEX hops, or wrapped assets | LayerZero OFT cross-chain transactions + Legacy Mesh |
| Liquidity shape | Fragmented per chain and bridge | Shared omnichain inventory model |
| Redemption root | Chain-specific issuer rules | Unlock Ethereum USDT via burn |
| Best mental model | Native USDT where issued | Omnichain representation of USDT |
USDT0 does not replace the need to understand major stablecoin types, issuer risk, or governance: the peg still ultimately depends on Tether’s reserves and redemption framework for USDT.
Source: https://tether.to/en/
USDT0 is aimed at three audiences:
Integrate one OFT contract-compatible USDT representation instead of maintaining many bridge adapters, so developers can build around an existing token path rather than launching a new token for every chain.
Use familiar fungible-token interfaces on each chain.
Ensure deployments on different chains are set as peers and correctly configured so contracts can send and receive verified messages.
Rely on issuer-style controls (for example freeze/blacklist capabilities where implemented) when compliance workflows require them.
Move balances between accounts on supported chains from a single mental model of “USDT0.”
Check the number of tokens, destination chain, and recipient details before you send funds.
Reduce repeated wrap/unwrap steps when rebalancing between L2s.
Still verify chain, contract, and UI authenticity before signing.
Support multi-chain deposits/withdrawals against a shared OFT design.
Avoid standing up bespoke bridge inventory for every new L2 listing.
Keep operational runbooks aligned with official deployments and Legacy Mesh routes.
Common acquisition paths:
Venue deposit/withdrawal: Use exchanges or L2 on-ramps that already list USDT0 on a supported network (Ink/Kraken was the first widely cited path).
Official transfer UI: Convert between USDT and USDT0 or move USDT0 across chains at usdt0.to/transfer; through the interface, you send a cross-chain message and should verify the recipient address before confirming.
DeFi swaps: Where liquidity exists, swap into USDT0 on destination-chain DEXs—always confirm the contract address against official deployments.
Wait for the message to be verified before treating the transfer as complete.
USDT0 can then be used in DeFi, payments, or treasury workflows on chains that accept the token. For yield-oriented follow-ups after you hold a stablecoin, Gate Learn covers stablecoin yield strategies separately.
USDT0 improves transfer plumbing, but several risks remain:
Cross-chain and smart-contract risk: USDT0 carries three layers of risk—Tether, LayerZero, and Everdawn—before bugs or operational failures in OFT messaging, adapters, and destination contracts. In a DVN, independent operators help attest message validity, but if that verification setup is weak, unauthorized minting risk rises. Governance, contract upgrades, and access control around key management are also part of the operational risk surface.
Regulatory uncertainty: Stablecoin rules differ by jurisdiction; omnichain features can raise extra compliance questions around travel-rule, custody, and tax treatment.
Adoption lag: Not every wallet, DEX, or exchange supports every USDT0 deployment on day one.
Competition: USDC, other fiat-backed coins, and synthetic dollars compete for the same settlement niche.
Liquidity unevenness: Even with a unified mint model, local DEX depth and venue support can be thin on newer chains; some deployments may also be wound down (follow official notices before using niche networks).
USDT0 is Tether’s LayerZero OFT-based omnichain representation of USDT. It locks USDT on Ethereum, mints USDT0 on supported chains, and uses Legacy Mesh to reach large legacy USDT footprints. Relative to classic bridged USDT, the design targets lower route friction and less fragmented inventory—while still inheriting messaging, contract, issuer, and regulatory risks. Check official deployments and transfer interfaces before moving size, and treat USDT0 as infrastructure for multi-chain USDT—not as a different dollar peg.
USDT0 is USDT made transferable across many blockchains through LayerZero’s OFT standard. Ethereum USDT is locked as collateral, and USDT0 is minted 1:1 on destination chains so users are not creating a separate unbacked wrapped coin.
Regular USDT is issued as native contracts on individual chains. USDT0 is an omnichain representation that moves with burn-and-mint messaging against locked Ethereum USDT, plus Legacy Mesh routes for major legacy deployments. Peg risk still traces back to Tether’s USDT reserves. On chains without a USDT0 deployment, users still interact with native USDT; where USDT0 is live, it serves as the omnichain representation rather than a separate dollar peg.
Support changes over time. USDT0 documentation lists on the order of 20+ native deployments (including Ink, Arbitrum, Polygon, Optimism, Berachain, Plasma, and others) and Legacy Mesh endpoints. Confirm the live deployments list and contract addresses before transferring.
USDT0 avoids depending on a third-party bridge liquidity pool for the base conversion, which removes one common failure mode. It does not eliminate smart-contract risk, and safety also depends on how LayerZero verification is configured and on who has upgrade access to the contracts, along with messaging-verification risk, phishing of fake contracts, or issuer/regulatory risk.
Typical paths are venue deposit/withdrawal on a supported network, the official USDT0 transfer portal, or destination-chain DEX swaps when liquidity exists. Redemption to Ethereum USDT works by burning USDT0 so locked USDT can be released through the OFT Adapter flow.
* The information is not intended to be and does not constitute financial advice or any other recommendation of any sort offered or endorsed by Gate.
* This article may not be reproduced, transmitted or copied without referencing Gate. Contravention is an infringement of Copyright Act and may be subject to legal action.





