Token features
USDT0 Network token contracts (USDT0, XAUT0, and USAT) share a common upgradeable ERC-20 implementation on most chains. Beyond the standard ERC-20 interface, the tokens support a set of signature-based features that enable gasless (meta-transaction) flows and smart contract wallet integrations. The following table summarizes each feature and links to its reference page:
| Feature | Standard | What it enables |
|---|---|---|
| Gasless approvals | EIP-2612 | Set an allowance with an off-chain signature instead of an approve transaction |
| Gasless transfers | EIP-3009 | Move tokens with a signed authorization that anyone, such as a relayer, can submit |
| Contract wallet signatures | EIP-1271 | Use gasless approvals and transfers from smart contract wallets (Safe, smart accounts), not only externally owned accounts (EOAs) |
| Crosschain mint and burn | ERC-7802 | Standardized interface the Omnichain Fungible Token (OFT) contract uses to mint and burn during cross-chain transfers |
Not every chain supports every feature. Some deployments use chain-native token frameworks (Hedera, Tempo), and the Polygon PoS token inherits constraints from the canonical contract it was upgraded from. Before you rely on a feature, check the availability matrix.
The shared implementation also has behavior that no single standard defines, such as batch transfers and a compliance blocklist. For details, see Additional token behavior.
Availability
The token contract deployed on each chain determines feature support — the contracts listed as Token in Deployments. The following matrices reflect the contracts as deployed in August 2026. The tokens are upgradeable, so a chain's feature set can change when its implementation is upgraded.
USDT0
| Chain | EIP-2612 Gasless approvals | EIP-3009 Gasless transfers | EIP-1271 Contract wallet signatures | ERC-7802 Crosschain mint/burn |
|---|---|---|---|---|
| Ethereum No token contract — the OFT Adapter locks USDT | N/A | N/A | N/A | N/A |
| Arbitrum One | Supported | Supported | Supported | Not supported |
| Berachain | Supported | Supported | Supported | Not supported |
| Conflux eSpace | Supported | Supported | Supported | Supported |
| Flare | Supported | Supported | Supported | Not supported |
| Hedera Native HTS token | Not supported | Not supported | Not supported | Not supported |
| HyperCore Non-EVM native spot asset | N/A | N/A | N/A | N/A |
| HyperEVM | Supported | Supported | Supported | Supported |
| Ink | Supported | Supported | Supported | Supported |
| Mantle | Supported | Supported | Supported | Supported |
| MegaETH | Supported | Supported | Supported | Supported |
| Monad | Supported | Supported | Supported | Supported |
| Morph | Supported | Supported | Supported | Supported |
| Optimism | Supported | Supported | Supported | Supported |
| Plasma | Supported | Supported | Supported | Supported |
| Polygon PoS Different EIP-712 signing domain | Supported 1 | Not supported | Not supported | Supported |
| Rootstock | Supported | Supported | Supported | Supported |
| Sei | Supported | Supported | Supported | Supported |
| Stable | Supported | Supported | Supported | Supported |
| Stellar Non-EVM Soroban contract | N/A | N/A | N/A | N/A |
| Tempo Native TIP-20 token | Supported 1 | Not supported | Not supported | Not supported |
| Unichain | Supported | Supported | Supported | Supported |
| XLayer | Supported | Supported | Supported | Supported |
1 Classic v, r, s permit only. Accepts signatures from externally owned accounts, but not EIP-1271 contract wallet signatures.
Chain-specific notes:
- Ethereum — there is no USDT0 token contract; the OFT Adapter locks and unlocks USDT, which has none of these features (see Ethereum source assets).
- Polygon PoS — USDT0 is the upgraded canonical PoS USDT contract. It supports only the classic
v, r, spermit, which accepts EOA signatures but not EIP-1271 contract wallet signatures. It also uses a different signing domain (see Signing domain). - Tempo — USDT0 is a native TIP-20 token implemented by the chain itself. It supports the classic
v, r, spermit through TIP-1004, with EOA signatures only. The other features are not part of TIP-20. - Hedera — USDT0 is a native Hedera Token Service (HTS) token. The address exposes the standard ERC-20 interface (reads,
transfer,approve,transferFrom) through Hedera's ERC-20 facade, but no signature-based features. - Arbitrum One, Berachain, and Flare — the deployed implementation predates ERC-7802.
- HyperCore and Stellar — these deployments don't run on the Ethereum Virtual Machine (EVM). HyperCore USDT0 is a native spot asset, and Stellar USDT0 is a Soroban contract with a classic asset wrapper. EVM signature standards don't apply there.
- Legacy Mesh chains (Tron, TON, Solana, and Celo) — these chains have no USDT0 token contract. Transfers there lock and unlock canonical USDT through the Arbitrum hub.
XAUT0 and USAT
Every XAUT0 EVM token contract — Arbitrum One, Avalanche, BNB Chain, Celo, Conflux eSpace, HyperEVM, Ink, Monad, Plasma, Polygon, and Stable — supports the full feature set, including ERC-7802. The HyperCore, Solana, and TON deployments are non-EVM: a native spot asset, a Solana Program Library (SPL) token, and a jetton, respectively. On Ethereum, the OFT Adapter locks XAUT (see Ethereum source assets).
The USAT token contract on Celo supports the full feature set, including ERC-7802. On Ethereum, the OFT Adapter locks USAT.
Ethereum source assets
On Ethereum, the OFT Adapters lock and unlock the original source assets, which have a more limited feature set. The adapters don't mint or burn, so ERC-7802 doesn't apply:
| Source asset | EIP-2612 Gasless approvals | EIP-3009 Gasless transfers | EIP-1271 Contract wallet signatures | ERC-7802 Crosschain mint/burn |
|---|---|---|---|---|
| USDT | Not supported | Not supported | Not supported | N/A |
| XAUT | Supported 1 | Not supported | Not supported | N/A |
| USAT | Supported 1 | Not supported | Not supported | N/A |
1 Classic v, r, s permit only. Accepts signatures from externally owned accounts, but not EIP-1271 contract wallet signatures.
Signing domain
The gasless approval and gasless transfer functions verify EIP-712 typed-data signatures. On every chain except Polygon PoS, they use the same domain:
const domain = {
name: await token.name(), // do not hardcode — token names vary across chains
version: '1',
chainId, // chain ID of the network the token is deployed on
verifyingContract: tokenAddress,
};
The Polygon USDT0 contract keeps the signing domain of the canonical PoS-bridged USDT it was upgraded from: a salt-based EIP-712 domain (EIP712Domain(string name,string version,address verifyingContract,bytes32 salt)) with no chainId field. A permit signed with the standard domain fails verification on Polygon. Use the following domain instead:
const polygonDomain = {
name: await token.name(), // do not hardcode — read the on-chain name
version: '1',
verifyingContract: tokenAddress,
salt: ethers.utils.hexZeroPad(ethers.utils.hexlify(137), 32), // chain ID as a bytes32 salt
};
For OFT interfaces and cross-chain transfer examples, see the Developer Guide. For contract addresses on every chain, see Deployments.