Cross-Chain Multisig (CCM)
The Cross-Chain Multisig (CCM) is the core contract that manages DAO governance across all connected networks. It is deployed at the same address on every chain: 0xCCCCcCCc42B7DA9fdEc1761698Fb55fdD41CDF55.
Batch Voting System
DAO decisions are grouped into batches. Token holders vote on each batch, and approved batches are executed across all chains.
Batches are connected by hashes in a chain-like structure — each batch references its predecessor. This creates an immutable, ordered history of governance decisions with strict sequential ordering across all EVM chains.
Batch N-1 (hash: 0xabc...)
└──▶ Batch N (prev: 0xabc..., hash: 0xdef...)
└──▶ Batch N+1 (prev: 0xdef..., hash: 0x123...)
This sequential ordering guarantees that every chain processes governance decisions in the exact same order, preventing conflicts or state divergence.
Propagation Mechanisms
Once a batch is approved, it must reach every connected chain. CCM supports two transport mechanisms:
| Mechanism | Description |
|---|---|
| Cross-chain multisig signing | Signers execute the batch directly on each target chain |
| Message bridging | Batch is relayed through a cross-chain messaging bridge |
Both mechanisms deliver the same deterministic batch payload, ensuring identical execution regardless of transport.
Recovery Mode
In edge cases where a batch exceeds the block size limit on a specific chain, CCM provides rescue batches. These allow the affected chain to process the oversized batch through an alternative execution path, preventing a single chain's constraints from blocking governance across the entire network.
Current vs Future Governance
| Aspect | Current Implementation | Future Implementation |
|---|---|---|
| Decision origin | Technical multisig signs on Mainnet | Fully on-chain governance contract |
| Batch creation | Multisig uploads batches to CCM | Governance contract creates batches directly |
| Trust model | Trusted multisig signers | Trustless on-chain voting |
The CCM contract itself does not change between phases — only the entity that submits batches transitions from a multisig to an on-chain governance contract.
Learn More
- Bytecode Repository (BCR) — How contract bytecode is stored and approved
- Instances — How per-chain deployments are activated and managed
- Contract Types & Versioning — How contracts are classified and versioned