USDT0 (USDT0) Price, Charts & Market Data

USDT0 is used to move USD₮ across blockchains while keeping one unified supply. It enables native cross-chain transfers under LayerZero’s Omnichain Fungible Token (OFT) standard, so users and applications can hold and transact a USD-pegged balance on multiple networks without relying on third-party wrappers. This supports payments, transfers and portfolio moves between chains while preserving fungibility with USD₮.

For day-to-day users, USDT0 is used to bridge USD-denominated value between supported networks to access lower transaction costs or different dApps, and to consolidate or redeploy balances without selling out of USD₮. Official documentation lists cross-chain transfers and liquidity mobility as primary uses. Fee policies are defined by the project (e.g., no extra fee for native OFT transfers; a 3 bps fee for certain “legacy mesh” routes), with gas paid on the chains involved. See “What are the fees, limits and typical cross-chain transfer times?” for details.

For exchanges, market makers and protocols, USDT0 is used to standardise USD₮ movement across multiple networks, simplify listings on new chains and reduce fragmented pools. The OFT model is designed to maintain a single global supply across chains, which helps unify liquidity and simplifies accounting for integrations that support the standard. See “Which networks are supported and what are the official contract addresses?” for implementation guidance on contracts and networks.

Developers use USDT0 as a stable settlement asset inside omnichain workflows. Because OFT abstracts cross-chain messaging and decimal handling, applications can build transfers, payments and settlement that span chains while treating USDT0 as one token. Technical references and quickstarts describe the transfer flows and contract patterns used.

USDT0 uses LayerZero’s Omnichain Fungible Token (OFT) standard to keep one unified supply of USD-denominated value across chains. When value moves from a source chain to a destination chain, USD₮ on the source is locked and the same amount of USDT0 is minted on the destination. Returning value burns USDT0 on the destination and releases the locked USD₮ on the source. The circulating USDT0 therefore matches USD₮ locked on-chain.

Step-by-step flow (high level):

1. Initiate transfer on the source chain’s USDT0/OFT contract with the destination chain and amount. The token logic is separated from cross-chain messaging so the token can remain stable while messaging libraries evolve.
2. Lock USD₮ on the source: USD₮ is escrowed in a smart contract (e.g., on Ethereum). This creates the backing for the outgoing mint.
3. Message verification & delivery via LayerZero v2: the transfer message is verified by a configurable set of Decentralized Verifier Networks (DVNs) and executed by an Executor on the destination chain. Projects choose their DVN quorum (X-of-Y-of-N) per route.
4. Mint on destination: once verified, the destination USDT0 contract mints the exact amount to the receiver. Decimal handling and chain differences are abstracted by the OFT standard.
5. Reverse path (burn-and-release): burning USDT0 on a chain triggers a verified message back; the escrowed USD₮ is released on the original chain to the designated recipient.

What this means in practice:

• One asset, many chains: OFT keeps a single global supply view rather than creating wrapped or synthetic variants. Users see 1 USDT0 everywhere, backed by USD₮ held on-chain. For network lists and contract addresses, see “Which networks are supported and what are the official contract addresses?”
• Deterministic accounting: at any time, USDT0 in circulation = USD₮ locked across the corresponding escrows; redemptions unwind that relationship. See “What backs USDT0 - how are reserves held and disclosed on-chain?” for on-chain monitoring resources.
• Messaging security is configurable: routes can use multiple DVNs and specify thresholds; this is part of the project’s security posture rather than token logic.

Note: USDT0’s OFT transfers follow the lock/mint model above. The project also references a “Legacy Mesh” path for certain existing USD₮ deployments that relies on credit locking/unlocking rather than mint/burn; integration details for that path are in the developer docs and are covered under “How does USDT0 differ from native USD₮ (Tether)?”

For fee behaviour, limits and expected confirmation times, please refer to “What are the fees, limits and typical cross-chain transfer times?”

Purpose & model:

• USD₮ (native): fiat-backed stablecoin issued by Tether on each supported chain; supply expands or contracts via Tether’s primary issuance/redemption.
• USDT0 (omnichain): an OFT (Omnichain Fungible Token) deployment that moves USD-denominated value across chains by locking USD₮ on a source chain and minting USDT0 on a destination; the reverse path burns and releases. It is designed to unify USD₮ liquidity rather than create a separate synthetic.

Supply accounting:

• USD₮ (native): total supply per chain is reported by Tether (transparency page).
• USDT0: circulating USDT0 across destination chains is backed 1:1 by USD₮ locked on-chain (typically on Ethereum) under the OFT model; the intent is one global view of the asset across multiple networks. See “What backs USDT0 - how are reserves held and disclosed on-chain?” for how to observe the lock/mint relationship.

Redemptions & conversions:

• USD₮ (native): eligible customers can redeem directly to fiat with Tether (subject to programme terms, KYC and minimums).
• USDT0: converts 1:1 with USD₮ across supported chains via the OFT flow; fiat redemption still occurs via USD₮ and Tether’s channels, not directly from USDT0.

Security model:

• USD₮ (native): standard token transfers on each chain; risk profile is that chain’s L1/L2 plus token contract controls.
• USDT0: cross-chain state changes are executed through LayerZero v2; message verification is provided by configurable Decentralized Verifier Networks (DVNs) and executed by an Executor on the destination chain. This separates token logic from messaging and lets routes choose quorum/thresholds.

Integration surface:

• USD₮ (native): token exists as independent deployments (ERC-20, TRC-20, etc.), each with its own contract and bridges depending on venue.
• USDT0: a single OFT interface across chains; exchanges, wallets and dApps can list/route USDT0 to reduce fragmented pools. Recent partner rollouts (e.g., X Layer/OKX) highlight deposit/withdraw flows directly in USDT0.

User experience & fees:

• USD₮ (native): moving between chains typically requires third-party bridges or exchange withdrawals.
• USDT0: uses the OFT transfer to move balances between chains while preserving the peg and avoiding wrapped variants; gas is paid on involved chains and any USDT0-specific fees are defined by the route/integration.

Bottom line: USDT0 is not a new stablecoin with separate reserves; it is an omnichain representation of USD₮ that standardises how USD₮ moves across chains via LayerZero’s OFT, while fiat issuance and redemption remain under Tether’s USD₮ programme.

Below are the official USDT0 deployments as listed in the project’s documentation as of September 2025. For safety, always verify on the linked block explorers from the same page before adding a token in your wallet or integration.

Current networks & addresses (official):

• Ethereum Mainnet (EID 30101) • OAdapterUpgradeable (Ethereum OFT adapter / locks USDT): 0x6C96dE32CEa08842dcc4058c14d3aaAD7Fa41dee • Safe: 0x4DFF9b5b0143E642a3F63a5bcf2d1C328e600bf8.

• Arbitrum One (EID 30110) • ArbitrumExtensionV2 (token extension): 0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9 • OUpgradeable (OFT): 0x14E4A1B13bf7F943c8ff7C51fb60FA964A298D92 • Safe: 0x4DFF9b5b0143E642a3F63a5bcf2d1C328e600bf8.

• Polygon PoS (EID 30109) • UChildUSDT0 (token): 0xc2132D05D31c914a87C6611C10748AEb04B58e8F • OUpgradeable (OFT): 0x6BA10300f0DC58B7a1e4c0e41f5daBb7D7829e13 • Safe: 0x4DFF9b5b0143E642a3F63a5bcf2d1C328e600bf8.

• Berachain (EID 30362) • TetherTokenOFTExtension (token): 0x779Ded0c9e1022225f8E0630b35a9b54bE713736 • OUpgradeable (OFT): 0x3Dc96399109df5ceb2C226664A086140bD0379cB • Safe: 0x425d1D17C33bdc0615eA18D1b18CCA7e14bEeb58.

• Ink (EID 30339) • TetherTokenOFTExtension (token): 0x0200C29006150606B650577BBE7B6248F58470c1 • OUpgradeable (OFT): 0x1cB6De532588fCA4a21B7209DE7C456AF8434A65 • Safe: 0xc95de55ce5e93f788A1Faab2A9c9503F51a5dAE2.

• Optimism (EID 30111) • TetherTokenOFTExtension (token): 0x01bFF41798a0BcF287b996046Ca68b395DbC1071 • OUpgradeable (OFT): 0xF03b4d9AC1D5d1E7c4cEf54C2A313b9fe051A0aD • Safe: 0x4DFF9b5b0143E642a3F63a5bcf2d1C328e600bf8.

• Unichain (EID 30320) • TetherTokenOFTExtension (token): 0x9151434b16b9763660705744891fA906F660EcC5 • OUpgradeable (OFT): 0xc07bE8994D035631c36fb4a89C918CeFB2f03EC3 • Safe: 0x4DFF9b5b0143E642a3F63a5bcf2d1C328e600bf8.

• Corn (EID 30331) • TetherTokenOFTExtension (token): 0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb • OUpgradeable (OFT): 0x3f82943338a8a76c35BFA0c1828aA27fd43a34E4 • Safe: 0x57d798f9d3B014bAC81A6B9fb3c18c0242A9411E.

• Sei (EID 30280) • TetherTokenOFTExtension (token): 0x9151434b16b9763660705744891fA906F660EcC5 • OUpgradeable (OFT): 0x56Fe74A2e3b484b921c447357203431a3485CC60 • Safe: 0x4DFF9b5b0143E642a3F63a5bcf2d1C328e600bf8.

• Flare (EID 30295) • TetherTokenOFTExtension (token): 0xe7cd86e13AC4309349F30B3435a9d337750fC82D • OUpgradeable (OFT): 0x567287d2A9829215a37e3B88843d32f9221E7588 • Safe: 0x6ae078461f35c3cC216A71029F71ee7Bc4d9a10b.

• HyperEVM (EID 30367) • HyperliquidExtension (token): 0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb • OUpgradeable (OFT): 0x904861a24F30EC96ea7CFC3bE9EA4B476d237e98 • Safe: 0xB64A89AD247a2D691A728Bb6822a85EeDD7Fc541.

• Rootstock (EID 30333) • TetherTokenOFTExtension (token): 0x779dED0C9e1022225F8e0630b35A9B54Be713736 • OUpgradeable (OFT): 0x1a594d5d5d1c426281C1064B07f23F57B2716B61 • Safe: 0x425d1D17C33bdc0615eA18D1b18CCA7e14bEeb58.

• XLayer (EID 30274) • TetherTokenOFTExtension (token): 0x779Ded0c9e1022225f8E0630b35a9b54bE713736 • OUpgradeable (OFT): 0x94bcca6bdfd6a61817ab0e960bfede4984505554 • Safe: 0x4DFF9b5b0143E642a3F63a5bcf2d1C328e600bf8.

For any updates, new networks or changes, use the “Deployments” section in the official docs as the source of truth.

Fees:

• Protocol fee (USDT0, native OFT routes): None. The project states there are no additional fees charged by USDT0 for native LayerZero OFT transfers. You still pay blockchain gas and LayerZero messaging costs (quoted at send time).
• Legacy Mesh routes (connecting legacy USDT deployments): 0.03% (3 bps) per transfer. This applies to specific paths that bridge legacy USDT and USDT0 networks (e.g., TON/Tron/Arbitrum/Ethereum).
• Gas & messaging costs: You fund normal source-chain gas and the LayerZero message execution on the destination. The OFT interfaces expose a fee quote so the dApp can show you the exact amount before you confirm.
• “No extra bridge fee” on some network integrations: Several network partners note that moving USDT0 onto their chain does not add extra bridging steps or fees beyond gas/messaging. Always verify within the interface for your chosen route. >Tip: The official transfer UI can airdrop destination gas for you when needed (you choose none/medium/max/custom), which is added to the quoted cost.

Limits:

• Protocol-level minimums/maximums: The USDT0 documentation does not specify global min/max transfer limits at the protocol level for native OFT routes. Any effective limits typically come from wallets, exchanges or custodians (e.g., withdrawal thresholds, compliance tiers). Check your venue’s policy if you hit a cap.
• Legacy Mesh: No global limits are documented in the public pages; treat venue-side constraints as the binding factor.

Typical transfer times:

• ETA shown in-app: The official UI displays an estimated time of arrival once you submit a transfer. Actual time depends mainly on source/destination chain finality and the chosen LayerZero route configuration (e.g., verifier quorum).
• What to expect: Under normal network conditions, most OFT transfers complete within minutes. Congestion, unusually slow finality or stricter verifier thresholds can extend this. If speed is critical, compare chains and routes in the UI before sending.

For the mechanics behind these costs and timings, see “How does USDT0 work (lock-and-mint / burn-and-release)?” For when a Legacy Mesh path is used instead of a native OFT route, details continue in “How do redemptions and conversions work, and where is liquidity available?”

Redemptions & conversions:

• Fiat redemption: USDT0 itself is not redeemed to fiat. Redemption to USD is done via USD₮ with Tether’s programme for eligible customers (account, KYC, minimums and fees per Tether). Practically, you would move USDT0 back to the chain holding the locked USD₮ (e.g., Ethereum) and then redeem USD₮ with Tether.
• USDT0 ⇄ USD₮ (on-chain): USDT0 uses an OFT flow. Moving “back” burns USDT0 on the destination chain and releases the locked USD₮ on the source chain; moving “out” locks USD₮ and mints USDT0. This maintains a 1:1 relationship between USDT0 in circulation and USD₮ locked. See “How does USDT0 work (lock-and-mint / burn-and-release)?” for mechanics.
• Legacy Mesh paths: For some legacy USD₮ deployments (e.g., Tron, TON), movement can use the Legacy Mesh (credit lock/unlock, no mint/burn). That route charges 0.03% (3 bps) per transfer and is meant to connect older USDT networks to the USDT0 fabric.

Where liquidity is available:

• Centralised venues: Exchanges integrating USDT0 support direct deposit/withdrawal of USDT0 on supported chains, simplifying cross-chain movement without third-party wrappers. Recent examples include OKX’s X Layer integration with deposits/withdrawals across Arbitrum, Optimism, Polygon, Unichain, Berachain and X Layer. Availability is venue-specific; check your exchange’s chain list.
• On-chain (DEXs & dApps): USDT0 is intended as the stable unit across supported networks; partners describe phasing out prior “bridged USDT” where applicable. For example, Flare notes bridged USDT via Stargate will be removed from the frontend and remains redeemable into USDT0 via Stargate Hydra. Liquidity then consolidates on USDT0 pairs. Liquidity venues vary by chain.
• Network coverage: The active chains and official contracts are listed in the project docs. Use those addresses (and linked explorers) to identify the correct USDT0 market per chain before supplying liquidity or integrating. See “Which networks are supported and what are the official contract addresses?”

Practical paths users take:

1. USDT0 → USD₮ → fiat: Burn USDT0 to release USD₮ on the source chain, then redeem USD₮ with Tether if you qualify.
2. USDT0 cross-chain reallocation: Use the OFT transfer to move stable balances between supported chains for market access or fees, without selling out of USD₮.
3. Legacy Mesh movement (where applicable): Use Mesh routes to connect legacy USD₮ networks into the USDT0 ecosystem; expect a 3 bps transfer fee.

For costs and timings of these paths, see “What are the fees, limits and typical cross-chain transfer times?”

USDT0 is backed 1:1 by USD₮ locked on Ethereum. When you send value out to another chain, USD₮ is escrowed in a contract on Ethereum and an equal amount of USDT0 is minted on the destination. Moving funds back burns USDT0 and releases the locked USD₮. This lock/mint–burn/release cycle is the source of backing for USDT0.

The escrow that holds USD₮ on Ethereum is the OAdapterUpgradeable contract (the OFT adapter). This contract is publicly visible on Etherscan; its USD₮ balance represents the on-chain collateral backing USDT0 that is currently in circulation across destination chains.

How to verify the backing yourself:

1. Confirm the Ethereum escrow address in the official docs (OAdapterUpgradeable).
2. On Etherscan, inspect the escrow’s USD₮ balance (token holdings tab). This should correspond to the aggregate USDT0 minted across other chains.
3. Optionally, on each destination chain, check the USDT0 token contract’s total supply to see how much has been minted there; the sum across chains ≈ USD₮ locked on Ethereum (allowing for in-flight messages). Contract addresses per chain are listed in “Which networks are supported and what are the official contract addresses?”

What is (and isn’t) disclosed:

• On-chain: the lock/mint relationship and escrowed USD₮ are observable on public explorers (Ethereum for the escrow; destination chains for USDT0 supply).
• Off-chain (underlying USD₮ reserves): the fiat-asset reserves that back USD₮ itself are reported by Tether on its Transparency pages and periodic assurance reports. USDT0 relies on those USD₮ reserves indirectly through the on-chain escrow. For reserve reporting, see Tether’s official transparency materials.

For the mechanics that maintain this relationship, see “How does USDT0 work (lock-and-mint / burn-and-release)?”

USDT0 is developed and operated by Everdawn Labs. Official materials on the USDT0 domain state Everdawn’s mission is to build the infrastructure layer that lets Tether assets scale natively across chains, and recent launch communications identify Everdawn Labs as the USDT0 operator.

Tether issues and redeems USD₮ and publishes reserve and circulation information. USDT0 relies on USD₮ that is locked on Ethereum and released on redemption; fiat redemptions happen through Tether’s programme, not directly via USDT0. USDT0 uses LayerZero v2 messaging and the OFT standard for cross-chain transfers. LayerZero provides the protocol, including Decentralized Verifier Networks (DVNs) and Executors; USDT0 configures a dual-DVN setup (LayerZero DVN + USDT0 DVN) for message verification. LayerZero does not issue the asset.

USDT0 publishes its technical architecture and contract roles (e.g., OAdapterUpgradeable on Ethereum and OUpgradeable/TetherTokenOFTExtension on destination chains) in the official docs. Admin operations are executed via published contracts and network-specific Safe setups listed on those documentation pages.

USDT0 maintains a public Immunefi bug bounty (up to $6,000,000) and lists completed audits by firms such as Guardian, ChainSecurity and Paladin in its security documentation.