Multichain Model
Multyr is designed to operate the same protocol architecture across multiple chains. Each chain runs an independent instance of the full stack — CoreVault, modules, strategies, and governance — with no cross-chain dependencies in the critical path.
Design Philosophy
The multichain model follows a principle of per-chain independence. Rather than bridging vault shares or synchronizing state across chains, each deployment is a self-contained system:
- Its own CoreVault with independent NAV and share accounting
- Its own set of strategy adapters targeting protocols available on that chain
- Its own governance parameters, roles, and timelocks
- Its own buffer, fee, and incentive configurations
This design eliminates bridge risk entirely. There is no mechanism for a failure on one chain to propagate to another.
Deployment Roadmap
| Chain | Asset | Status |
|---|---|---|
| Arbitrum | USDC | Shadow testing |
| Base | USDC | Planned |
| Optimism | USDC | Planned |
| Ethereum | USDC | Planned |
| Polygon | USDC | Planned |
| Avalanche | USDC | Planned |
| BSC | USDC | Planned |
Arbitrum is the first deployment, currently in shadow testing. Subsequent chains will follow the same deployment lifecycle: factory deployment, configuration, shadow testing, and production launch.
Per-Chain Independence
Each chain's deployment operates autonomously:
- Strategies are chain-specific. Aave V3 on Arbitrum and Aave V3 on Base are separate strategy adapters targeting separate protocol deployments.
- Governance is chain-specific. Fee parameters, allocation targets, and operational roles are configured independently per chain.
- Vault shares are chain-specific. There is no bridging of vault shares between chains. A depositor on Arbitrum holds Arbitrum vault shares; a depositor on Base holds Base vault shares.
- NAV is chain-specific. Each vault's share price reflects only the assets deployed on its chain.
Cross-Chain Considerations
Multyr intentionally avoids cross-chain complexity in its core protocol:
- No share bridging. Vault shares exist only on their native chain. This eliminates an entire class of bridge-related risks.
- No cross-chain rebalancing. Capital deployed on one chain is never moved to another chain by the protocol.
- No shared state. Each chain's StrategyHealthRegistry, BufferManager, and FeeCollector operate on local data only.
Global governance decisions (such as economic policy, security standards, and fee structures) are coordinated off-chain and applied per-chain through each deployment's own governance process.
Chain Selection Criteria
New chain deployments are evaluated based on:
- DeFi liquidity depth — sufficient USDC liquidity and lending market depth to support meaningful strategy deployment
- Protocol availability — presence of target lending protocols (Aave, Euler, Morpho, Compound, and others) with established track records on the chain
- User demand — demonstrated depositor interest and ecosystem activity
- Governance approval — each new chain deployment requires governance authorization
Document version: 1.1 Last updated: 2026-03-29