The Problem
Traditional tokens face critical limitations in a multichain world:- Asset Isolation: Tokens trapped on their origin chains
- Fragmented Liquidity: Multiple wrapped versions across different networks
- Complex Deployments: Expensive and time-consuming multi-chain launches
- Poor UX: Users confused by different token addresses on each chain
- Security Risks: Third-party bridges controlling token movement
How It Works
Hub-Spoke Architecture
Metatoken uses a Hub-Spoke model with specialized contracts:- MetaERC20Hub: Deployed on the token’s home chain, locks/unlocks canonical tokens
- MetaERC20Spoke: Deployed on remote chains, mints/burns synthetic tokens
- Security Threshold Routing: High-value spoke-to-spoke transfers routed through hub for validation
Transfer Flows
- Hub → Spoke: Lock canonical tokens on hub, mint synthetic tokens on spoke
- Spoke → Hub: Burn synthetic tokens on spoke, unlock canonical tokens on hub
- Spoke → Spoke (Low Value): Direct burn and mint between spokes
- Spoke → Spoke (High Value): Routed through hub with validator approval for security
Key Benefits
- Unified Supply: Single global token supply, no wrapped token confusion
- Capital Efficient: No liquidity pools or slippage, always 1:1 exchange
- Deterministic Addresses: Same contract address on every chain
- Security Controls: Configurable thresholds and validator approval for high-value transfers
- Emergency Recovery: Admin functions for handling stuck transfers while maintaining conservation of funds
- Cost-Effective: Included with Caldera rollup deployments
Deployment
MetaTokens are currently deployed and managed by Caldera. This ensures proper security configuration, validator setup, and integration with the Metalayer infrastructure. Projects interested in deploying their token as a MetaToken should contact our team to discuss requirements, timeline, and integration process.Next Steps
Contact Team
Discuss omnichain token deployment
Protocol Reference
Review contract architecture