zk-layer-vote

This repo contains source files of a cross-chain voting protocol for ETHGlobal Istanbul 2023.

Frontend

https://6559b054b025a87e3173ea8c--zk-layer-vote.netlify.app

Installation

Frontend module

1. npm install - Install all dependencies
2. npm run build - Build the project
3. npm start - Start the frontend server

Backend module

1. npm install - Install all dependencies
2. docker-compose up - Run Redis in Docker
3. npm start - Start the backend server

On-chain module

1. npm install - Install all dependencies
2. hardhat compile - Compile the smart contracts
3. hardhat migrate - Deploy the smart contracts

ZK Proof generator

1. npm install - Install all dependencies
2. node generate.js - Generate the zero-knowledge proofs

Deployments

Twitter

• Gnosis Twitter Announce

Contract addresses

Sepolia

• VotesTokenL1 - 0x4d389dA3786036ee0b9aba8E4B99891a925d88D0
• GovernerL1 - 0xD7A1DC78F0E90Ab2645E1DbECf6135D17c7dA411
• StateRootL1 - 0xbb8c8E79c34C6420716A6937bF7E3B9226Cc81f5

Scroll-sepolia

• TokenL2 - 0xC007267DF5f0f7aEc5fb90CF03b56F051Bc6C89e
• DelegateL2 - 0x4d389dA3786036ee0b9aba8E4B99891a925d88D0

XDC-testnet

• TokenL2 - 0xbb8c8E79c34C6420716A6937bF7E3B9226Cc81f5
• DelegateL2 - 0x491A7D1A203980Fd5d2cdE093893FcdCf994291e

Arbitrum-sepolia

• TokenL2 - 0xC007267DF5f0f7aEc5fb90CF03b56F051Bc6C89e
• DelegateL2 - 0x4d389dA3786036ee0b9aba8E4B99891a925d88D0

Polygon-zkEVM-testnet

• TokenL2 - 0xC007267DF5f0f7aEc5fb90CF03b56F051Bc6C89e
• DelegateL2 - 0x4d389dA3786036ee0b9aba8E4B99891a925d88D0

Gnosis-mainnet

• TokenL2 - 0xbb8c8E79c34C6420716A6937bF7E3B9226Cc81f5
• DelegateL2 - 0x491A7D1A203980Fd5d2cdE093893FcdCf994291e

Celo-alfajores

• TokenL2 - 0xC007267DF5f0f7aEc5fb90CF03b56F051Bc6C89e
• DelegateL2 - 0x4d389dA3786036ee0b9aba8E4B99891a925d88D0

Base-goerli

• TokenL2 - 0x6c9373BaD4d213Ea0C796cCF039102B43341df24
• DelegateL2 - 0x507d16b08562Bc341775657C18eA2123EFc69FD1

Linea-testnet

• TokenL2 - 0xC007267DF5f0f7aEc5fb90CF03b56F051Bc6C89e
• DelegateL2 - 0x4d389dA3786036ee0b9aba8E4B99891a925d88D0

Introduction

Problem

• For voting in DAO protocols, voting tokens (VTs) are required.

• What happens if VTs are scattered across multiple networks simultaneously?

• Two problems arise:

  1. The complexity of synchronizing voting results from multiple networks concurrently.
  2. The inability to deploy VTs in other networks due to bridge architecture limitations (converting VTs into ERC20 tokens).

Examples

• Uniswap V3 | UNI token | OpenZeppelin Governor + Snapshot
• Lido V2 | LDO token | Aragon
• Curve | CRV token | Aragon
• ENS | ENS token | Snapshot + Tally
• Balancer | BAL token | Snapshot
• … and any other protocols with a VTs in L1 that lack implementations in L2.

Solution

A crosschain governance protocol that:

1. Uses a trustless & universal architecture supporting multiple L2 networks, with VT on L1.

2. Uses default ERC-20 to eliminate conflicts in the bridge architecture.

3. Shifts the execution of L2-voting mechanisms to the ZKP-module, instead of using VT.

4. Implements ZKP to validate the accurate delivery of L2 State data.

Architecture

Step 1. VT → Bridge → ERC-20

Step 2. We use standard ERC-20 (or delegate storage), aggregate information about balances recorded in the snapshot, and send it to the Frontend for further use.

Step 3. Through the Frontend, the Proof Generator receives information about ChainId, Voter Address, and Vote; based on these values, the Proving System generates a SNARK proof and commits it to the votes aggregator on L1.

Step 4. The main Voting Contract accounts for votes from all networks, incorporates them into the quorum, and distributes them across the proposal options. Voting is finished.

Demonstration

Future track

1. Improving SNARK proofs aggregation.

2. Implementing custom plugins for voting mechanisms:

   • OpenZeppelin Governor | Ethereum | link
   • Aragon | Ethereum | link
   • Tally | Ethereum | link
   • Guild | Ethereum | link
   • Llama | Ethereum | link
   • Colony | Ethereum | link
   • Snapshot | Ethereum | link