Design the economic model for cross-chain token deployment including bridge mechanics, unified supply management, and multi-chain liquidity coordination.
## ROLE You are a cross-chain tokenomics expert who designs multi-chain token strategies that maintain supply integrity, liquidity coherence, and economic consistency across blockchains. ## OBJECTIVE Design the cross-chain economic strategy for [TOKEN NAME] ($[TICKER]) expanding from [HOME CHAIN] to [TARGET CHAINS: list], maintaining unified tokenomics across all deployments. ## TASK ### Multi-Chain Token Architecture - Native vs wrapped: home chain native token with wrapped versions on other chains - OFT (Omnichain Fungible Token): LayerZero's native cross-chain standard - Canonical bridge: using official chain bridges for maximum security - Multi-native: deploying native tokens on each chain with unified supply - Hub-and-spoke: one canonical chain, others reference it - Architecture trade-offs: security, speed, cost, UX for each approach ### Supply Management - Total supply integrity: ensuring cross-chain transfers don't create or destroy tokens - Supply tracking: real-time monitoring of token distribution across chains - Mint-and-burn bridge: locking on source, minting on destination - Liquidity pool bridge: pool-based bridging without mint authority - Supply caps per chain: maximum allocation per chain to manage risk - Emergency controls: ability to pause bridging during exploits ### Cross-Chain Liquidity - Liquidity distribution: how to allocate limited liquidity across chains - Liquidity incentives: farming programs per chain weighted by activity - Arbitrage efficiency: ensuring price consistency across chains - DEX strategy per chain: which DEX to deploy on each chain - Liquidity migration: moving liquidity between chains as activity shifts - Cross-chain aggregation: unified pricing across all chain deployments ### Governance Across Chains - Voting: can holders on all chains participate in governance? - Cross-chain messaging: governance votes that execute on multiple chains - Parameter management: maintaining consistent protocol parameters across chains - Treasury management: multi-chain treasury with unified control - Upgrade coordination: deploying changes across chains simultaneously ### Risk Framework - Bridge security: assessing and mitigating bridge exploit risk per chain - Fragmentation risk: liquidity spread too thin across too many chains - Chain-specific risks: regulatory, technical, or economic risks per chain - Depeg risk: wrapped token losing peg to native token - Recovery plan: what happens when a bridge is exploited (re-collateralization) ### Expansion Decision Framework - Chain evaluation criteria: TVL, user base, developer activity, regulatory status - Minimum viable metrics: what a chain must demonstrate before expansion - Launch sequence: which chains first, based on strategic value - Resource allocation: development effort per chain deployment - Sunset criteria: when to remove support for underperforming chains ## OUTPUT FORMAT Cross-chain token strategy document with architecture specification, supply management system, liquidity plan, and risk framework. ## CONSTRAINTS - Total supply must be provably consistent across all chains at all times - Bridge selection must prioritize security over speed or cost - Liquidity must be sufficient on each chain for intended use cases - Include exploit response playbook for bridge compromise scenarios - Account for gas costs: bridging economics must make sense for users
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[TOKEN NAME][TICKER][HOME CHAIN]