Multichain Support

Deployment Model

CVE maintains consistent behavior and utility across all supported chains through a dual-implementation approach:

Chain-Specific Contract Implementations:

  • CVE.sol: The canonical implementation deployed on the primary chain with full token allocation management

  • RemoteCVE.sol: Simplified implementation deployed on secondary chains

  • Both implementations inherit from CVEBase.sol which provides core cross-chain functionality

Unified Accounting:

  • The protocol maintains consistent accounting of CVE supply through _burn()/_mint() patterns in the bridge functions

  • completeBridge() in CVEBase.sol ensures proper token minting on destination chains

  • Total supply remains consistent across the ecosystem through controlled minting and burning

Chain Agnostic Value:

  • CVE maintains equivalent value through the MessagingHub contract that coordinates cross-chain communication

  • Each implementation uses identical name() and symbol() functions returning "Curvance Collective" and "CVE"

Cross-Chain Operations

The multichain nature of CVE enables several important protocol functions:

Chain Incentives:

  • Creates economic incentives for ecosystem expansion through native CVE on each chain

  • Each chain participates equally in the tokenomics through consistent implementation

Token Migration:

  • Users can move their CVE tokens between chains using bridge() function

  • payloadType value of !=4 designates CVE token migrations in the bridgeToken() function in MessagingHub.sol

Implementation Details

The multichain support for CVE includes:

Chain Registration:

  • New chains are registered through the CentralRegistry contract

  • messagingHub address is stored in the central registry via centralRegistry.messagingHub()

Bridge Configuration:

  • Each chain pair uses bridgeFee() function to calculate required message fees

  • The quoteMessageFee() function in IMessagingHub determines exact costs

Continuous Operation:

  • The _getMessagingHub() internal function ensures the correct messaging hub is always used

This multichain architecture enables Curvance to offer a truly unified DeFi experience across multiple blockchains while maintaining the integrity and utility of the CVE token throughout the ecosystem.

Last updated