Cross-chain Gov

A cross-chain DAO framework that allows synchronization across multiple EVM networks.

Overview

Cross-chain Gov enables DAOs to manage operations across multiple blockchains while maintaining consistent governance parameters, membership, and decisions. The system uses a home chain as the source of truth, with cross-chain proofs to synchronize state changes to foreign chains.

Watch the Asciinema video.

Motivation

Provide a coordination tool that fits the needs of regular users.

• Gov contracts (Hardhat)
• Documentation
• Gov UI
• Gov UI repo
• Gov Deployer
• Gov Deployer repo
• Example DAO on Tally

Features

• Synchronization of cross-chain governance parameters
• Non-transferable membership NFTs with voting capabilities
• DAO manifesto management across chains
• Secure proof generation and verification for cross-chain operations

Getting Started

Prerequisites

• Foundry
• Bun
• supersim

Installation

# Clone the repository
git clone https://github.com/w3hc/gov-crosschain.git
cd gov-crosschain

# Install dependencies
bun install

# Build the project
forge build

Testing

Run the basic test suite:

forge test

Deployment

In this demo, we:

• Deploy the factories to local OP and base
• Deploy a DAO to local OP and base
• Add a new member on home chain (OP)
• Sync membership on Base

Deploy with Supersim

Launch local OP and Base:

supersim fork --chains=op,base --interop.enabled

Then in another terminal,

Deploy the factories to op (chain A) through Safe Singleton Deployer:

forge script script/DeployFactories.s.sol --rpc-url op --broadcast

Deploy the factories to base (chain B):

forge script script/DeployFactories.s.sol --rpc-url base --broadcast

Note: We deploy from a static wallet private key, but please note anyone can deploy the factories to any compatible network.

Now deploy a DAO to op through the factory contracts with OP as home chain:

forge script script/DeployDAO.s.sol --rpc-url op --broadcast

And deploy the DAO to base:

forge script script/DeployDAO.s.sol --rpc-url base --broadcast

Call propose on op:

forge script script/AddMemberProposal.s.sol --rpc-url op --broadcast

Then follow the instructions:

• Alice votes
• Bob votes
• We execute the proposal
• We verify if Francis is a DAO member on chain A
• We generate a proof on chain A
• We claim the proof on chain B
• We verify if Francis is a DAO member on chain B

Deploy to mainnets

Update your .env file with your configuration:

cp .env.example .env
# Edit .env with your API keys and mnemonic

Deploy the factories:

forge script script/Deploy.s.sol --rpc-url op_mainnet --broadcast --verify

Then anyone can deploy the factories at the same contract addresses to any other EVM network that's supporting the Safe Singleton Deployer.

Deploy your DAO:

forge script script/Deploy.s.sol --rpc-url base_mainnet --broadcast --verify

Usage

1. Deploy the NFT and Governance contracts on your home chain
2. Deploy the same contracts on all foreign chains
3. Use governance to make decisions on the home chain
4. Generate proofs for cross-chain synchronization
5. Apply the proofs on foreign chains to maintain consistency

Architecture

The system consists of two main contracts:

• Gov.sol: Handles governance operations, voting, and parameter management
• NFT.sol: Manages DAO membership and voting power

The cross-chain synchronization flow:

1. Changes occur on the home chain through governance
2. Proof is generated for the change
3. Proof is submitted to foreign chains
4. Foreign chains verify and apply the change

Key Operations

Governance

• Update DAO manifesto
• Modify voting parameters
• Add/remove members
• Create and vote on proposals

Cross-Chain Management

• Generate proofs for parameter changes
• Generate proofs for membership changes
• Claim and verify proofs on foreign chains

Security Considerations

• The home chain (Optimism) serves as the source of truth.
• All operations on foreign chains require cryptographic proof verification
• Membership NFTs are non-transferable to maintain governance integrity
• All sensitive operations require governance approval

Support

Feel free to reach out to Julien on Farcaster, Element, Status, Telegram, Twitter, Discord, or LinkedIn.

Credits

I want to thank Paul Razvan Berg for his work on the Foundry template we used.

License

This project is licensed under the GNU General Public License v3.0.