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.
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 Abstraction: Works with both standard EVM wallets and ERC-4337 smart accounts
- Fee Management: Built-in fee calculation and bridge cost estimation
- Token Support: Supports USD₮0 and XAU₮0 ecosystem tokens
- 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 Flexibility: Works with JSON-RPC URLs and EIP-1193 browser providers
Supported Networks
Source Chains (EVM)
| Chain | Chain ID |
|---|---|
| Ethereum | 1 |
| Arbitrum | 42161 |
| Optimism | 10 |
| Polygon | 137 |
| Berachain | 80094 |
| Ink | 57073 |
| Plasma | 9745 |
| Conflux eSpace | 1030 |
| Corn | 21000000 |
| Avalanche | 43114 |
| Celo | 42220 |
| Flare | 14 |
| HyperEVM | 999 |
| Mantle | 5000 |
| MegaETH | 4326 |
| Monad | 143 |
| Morph | 2818 |
| Rootstock | 30 |
| Sei | 1329 |
| Stable | 988 |
| Unichain | 130 |
| XLayer | 196 |
Destination Chains
All source chains above, plus:
| Chain | Endpoint ID (EID) |
|---|---|
| Solana | 30168 |
| TON | 30343 |
| TRON | 30420 |
Non-EVM route candidates
For auto-resolved routes toward Solana, TON, or TRON, beta.7 skips the source chain's ordinary oftContract. The bundled configuration can instead consider these source contracts:
| Source token contract family | EVM source chains with a bundled candidate |
|---|---|
| USD₮0 legacy mesh | Ethereum, Arbitrum, Celo |
| XAU₮0 OFT | Ethereum, 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. The ERC-4337 flow bundles token approval and the helper call into one UserOperation.
ERC-4337 fee and bridgeFee values can use different denominations in 1.0.0-beta.7. Review the fee-unit limitation before configuring bridgeMaxFee.
Next Steps
Node.js Quickstart
Get started with WDK in a Node.js environment
Configuration
Configure the Bridge USD₮0 EVM Protocol
API Reference
Complete API documentation for the bridge protocol
Usage
Installation, quick start, and usage examples