For the background and Hedera’s perspective on why this matters, read the announcement: Hedera integrates USDT0 for crosschain stablecoin liquidity.
What USDT0 is (and what it is not)
What USDT0 IS
- Native USDT liquidity on Hedera, backed 1:1 by Tether’s USDT
- A single omnichain token, the same asset across every supported chain
- Built on LayerZero’s OFT standard for secure cross-chain messaging
- On Hedera, a standard HTS fungible token with an EVM-compatible interface
What USDT0 is NOT
- Not a wrapped or synthetic token with its own separate liquidity pool
- Not a third-party bridge that issues a chain-specific IOU
- Not a new stablecoin with a separate peg or reserve from USDT
- Not custodied by Hedera or the LayerZero messaging layer
How it works
USDT0 uses a lock-and-mint model anchored on Ethereum and an omnichain messaging layer to keep one unified supply across chains.USDT locks on Ethereum
The canonical USDT supply is held by an OFT Adapter contract on Ethereum mainnet. Locking USDT there authorizes an equivalent mint elsewhere.
USDT0 mints on the destination chain
An equivalent amount of USDT0 mints on the destination chain (such as Hedera) with strict 1:1 backing.
Transfers move over LayerZero
A cross-chain transfer burns USDT0 on the source chain and mints it on the destination chain. LayerZero’s decentralized verifier network carries and validates the message, so no separate bridge liquidity pool is involved.
USDT0 on Hedera
On Hedera, USDT0 is a native Hedera Token Service (HTS) fungible token that is also reachable through its EVM address, so you can work with it from both native SDKs and EVM tooling such as ethers.js, Hardhat, or Foundry.| Detail | Value |
|---|---|
| Token name | USDT0 |
| Decimals | 6 |
| Hedera token ID | 0.0.10282787 |
| Token EVM address | 0x00000000000000000000000000000000009Ce723 |
| OFT contract (cross-chain send/receive) | 0xe3119e23fC2371d1E6b01775ba312035425A53d6 |
| LayerZero endpoint ID (EID) for Hedera | 30316 |
| Hedera EVM chain ID | 295 (mainnet) |
Sending USDT0 across chains
Cross-chain transfers go through the OFT contract, not a plain ERC-20transfer. The flow is the same as any LayerZero OFT: quote the messaging fee, approve the amount if needed, then call send. You pay the LayerZero messaging fee in the source chain’s native gas token (HBAR when sending from Hedera).
The code below illustrates the standard LayerZero OFT pattern so you can see the shape of the flow. It is not a Hedera-tested recipe. Treat the USDT0 Developer Guide as the source of truth for working integration code — it ships maintained TypeScript/ethers.js examples — and verify the Hedera-specific behavior noted below before moving real value.In particular, mind the tinybar/weibar unit difference:
quoteSend returns the fee in tinybars (8 decimals), but the JSON-RPC relay expects msg.value in weibars (18 decimals), so the fee must be converted before it is attached to send. See Developer Considerations on the LayerZero page for more on this.send function takes a SendParam struct and a MessagingFee:
SendParam
Example: send USDT0 from Hedera with ethers.js
send-usdt0.js
amountLD and minAmountLD are expressed in USDT0’s 6 decimals, so 100 USDT0 is 100_000000. USDT0’s OFT uses 6 shared decimals, matching its 6 local decimals, so there is no dust removal or rounding on transfer; the full amount you send is delivered. The LayerZero messaging fee is paid separately in HBAR (the nativeFee), not deducted from the transferred USDT0.Common destination endpoint IDs
Use the destination chain’s LayerZero endpoint ID (EID) asdstEid. A few common values:
| Destination chain | Chain ID | LayerZero EID |
|---|---|---|
| Ethereum | 1 | 30101 |
| Arbitrum One | 42161 | 30110 |
| Optimism | 10 | 30111 |
| Polygon PoS | 137 | 30109 |
| Hedera | 295 | 30316 |
Using USDT0 as a regular token on Hedera
Once USDT0 is on a Hedera account, it behaves like any other HTS fungible token for in-network use. You can transfer it between Hedera accounts, hold it in smart contracts, and use it in DeFi protocols using either the native SDKs or the EVM interface:- Native SDKs: use
TransferTransactionwith the token ID0.0.10282787, and associate the token first if needed. - EVM tooling: treat the token EVM address
0x00000000000000000000000000000000009Ce723as a standard 6-decimal ERC-20.
send flow for moving USDT0 across chains; a same-chain Hedera transfer is just a normal HTS or ERC-20 transfer.
Requirements and limitations
- The USDT0 token is mainnet-only: USDT0 is deployed on Hedera mainnet; there is no Hedera testnet USDT0 token to test transfers against. LayerZero’s messaging layer itself does have a Hedera testnet endpoint (EID 40285), so you can exercise OFT wiring on testnet with your own token. Validate the USDT0 path with small amounts on mainnet.
- HBAR for fees: Sending USDT0 from Hedera requires HBAR to cover both the Hedera transaction fee and the LayerZero messaging fee (the
nativeFeeyou attach asmsg.value). - Token association: A receiving Hedera account must be associated with USDT0 (or have an open auto-association slot) before it can hold a balance.
- 6 decimals: USDT0 uses 6 decimals on every chain, and its OFT uses 6 shared decimals, so cross-chain transfers move the exact amount with no dust rounding.
- Destination gas: Cross-chain delivery may require execution options (
extraOptions) that allocate enough gas on the destination chain. UsequoteSendto price the transfer with the options you intend to use. - Confirm addresses: Always verify contract addresses and endpoint IDs against the canonical USDT0 deployments page before integrating.
Resources
USDT0 documentation
Official USDT0 technical documentation, architecture, and developer guide.
USDT0 developer guide
Maintained TypeScript/ethers.js integration examples — the source of truth for working code.
USDT0 deployments
Canonical contract addresses and endpoint IDs for every supported chain.
Hedera integrates USDT0
Hedera’s announcement covering the what and why.
LayerZero on Hedera
The OFT, OFT Adapter, and HTS Connector building blocks USDT0 is built on.
LayerZero OFT standard
How the Omnichain Fungible Token standard works under the hood.