WDK logoWDK documentation
StartWalletsDeFi & FiatAI & CLITools

Bridge tokens with USD₮0

Bridge USD₮0 and XAU₮0 across supported EVM and non-EVM destinations from WDK accounts.

Use the USD₮0 bridge module to move USD₮0 and XAU₮0 across supported chains from WDK EVM wallet accounts. To bridge from a Solana account, use the Solana bridge module.

These pages reflect @tetherto/wdk-protocol-bridge-usdt0-evm@1.0.0-beta.13. When the ERC-4337 helper is used, quotes and submissions include its surcharge as tokenFee in source-token base units. The LayerZero bridgeFee is in source-chain native base units. Recipient validation covers EVM, Solana, TON, and TRON during both quote and execution.

The bridge requires the account’s RPC URL or an EIP-1193 provider with request(). Manager-derived accounts that retain an ethers Provider in their configuration cannot be passed directly. Use the corresponding direct account constructor with its original RPC URL or genuine EIP-1193 input; never mutate internal provider fields. Direct accounts bypass WDK middleware and the Policies plugin, so retain required application checks and account-level controls.

Features

  • Cross-Chain Bridge: Move USD₮0 tokens between supported blockchains
  • LayerZero Integration: Uses LayerZero protocol for secure cross-chain transfers
  • Expanded Multi-Chain Support: Discover 25 configured EVM and non-EVM network keys
  • Non-EVM Destinations: Bridge toward Solana, TON, and TRON when the source token has a compatible route contract
  • Account Compatibility: Accepts the shared WDK account interfaces; execution requires a callable sendTransaction() method and EVM transaction support. ERC-4337 helper batching also requires the exact concrete wallet class used by the bridge. See account requirements.
  • Fee Management: Built-in fee calculation and bridge cost estimation
  • Token Support: Standard EVM accounts support configured USD₮0 and XAU₮0 routes. ERC-4337 quotes and execution require the source OFT's token to match the transaction-value helper's token; current helpers support USD₮0, and XAU₮0 is rejected.
  • Route Overrides: Custom OFT contract addresses and destination endpoint IDs
  • TypeScript Support: Full TypeScript definitions included
  • Memory Safety: Secure transaction handling with proper error management
  • Provider Inputs: Works with JSON-RPC URLs and EIP-1193 providers retained by a directly constructed account

Supported Networks

Source Chains (EVM)

ChainChain ID
Ethereum1
Arbitrum42161
Optimism10
Polygon137
Berachain80094
Ink57073
Plasma9745
Conflux eSpace1030
Corn21000000
Avalanche43114
Celo42220
Flare14
HyperEVM999
Mantle5000
MegaETH4326
Monad143
Morph2818
Rootstock30
Sei1329
Stable988
Unichain130
XLayer196

Destination Chains

All source chains above, plus:

ChainEndpoint ID (EID)
Solana30168
TON30343
TRON30420

Non-EVM route candidates

For auto-resolved routes toward Solana, TON, or TRON, the protocol skips the source chain's ordinary oftContract. The bundled configuration can instead consider these source contracts:

Source token contract familyEVM source chains with a bundled candidate
USD₮0 legacy meshEthereum, Arbitrum, Celo
XAU₮0 OFTEthereum, Arbitrum, Avalanche, Celo, HyperEVM, Ink, Monad, Plasma, Polygon, Stable

This table shows source-side contract availability, not a guarantee that every listed source reaches every non-EVM destination. The selected contract must support the destination endpoint on-chain. Confirm the exact source-token-destination route with quoteBridge() before execution, or provide a verified route-specific oftContractAddress and optional dstEid.

getSupportedChains() and getSupportedTokens() read the static chain and token configuration. They do not validate a source-to-destination pair or prove that its LayerZero peer is configured.

Token support is determined by the contracts deployed on each chain. The protocol checks for oftContract, legacyMeshContract, and xautOftContract to determine available tokens.

Standard EVM accounts can use every supported EVM source route with a matching token deployment. ERC-4337 helper bridging is available from Ethereum, Arbitrum, Plasma, and Polygon when the exact package identity requirement is satisfied. That flow bundles token approval and the helper call into one UserOperation.

ERC-4337 bridgeFee uses source-native base units. Token-paid gas still returns fee in paymaster-token units, so that mode mixes denominations in fee + bridgeFee and cannot provide a meaningful single-currency bridgeMaxFee spending cap. Native-gas and sponsored flows use compatible units; see the fee-unit limitation.

Next Steps


Need Help?

On this page