Skip to main content

​
Deployed Contracts

This page lists the official addresses for CreateDAO v2 contracts on supported blockchain networks. All contracts use deterministic CREATE2 deployment for consistent addresses across chains.
CreateDAO v2 is a complete rewrite using OpenZeppelin Governor. These addresses are NOT compatible with v1 contracts.

​
Contract Architecture

Each network has:
  1. DAOFactory - The main factory contract for creating new DAOs
  2. DAOToken Implementation - Shared implementation for all DAO tokens (EIP-1167 clones)
  3. DAOGovernor Implementation - Shared implementation for all governors (EIP-1167 clones)
When you create a DAO, the factory creates minimal proxies (45 bytes each) that delegate to these implementations.

​
Mainnet Deployments

​
Base (Mainnet)

ContractAddressExplorer Link
DAOFactory0xd141662F4b788F28B2a0769a6d3f243D046B571fView on Basescan
DAOToken Implementation0xfAAB628eddeEC6093CCdB5288b865a8073ab55DbView on Basescan
DAOGovernor Implementation0x2F81fb483fD1B578d16d41e92c62A365b4b04081View on Basescan
Example DAO on Base:
ContractAddressExplorer Link
DAOToken (Proxy)0x154EB315Ab729E998847aA55F8b5bC73cf8A61d9View on Basescan
DAOGovernor (Proxy)0x4013cdFEB389A4213e8565258D2ac3604bFbB1B3View on Basescan
TimelockController (Treasury)0xb8CE0BbD2c5B589Da458677392B255E761E1A15FView on Basescan

​
Testnet Deployments

​
Sepolia (Ethereum Testnet)

ContractAddressExplorer Link
DAOFactory0xd141662F4b788F28B2a0769a6d3f243D046B571fView on Etherscan
DAOToken Implementation0xfAAB628eddeEC6093CCdB5288b865a8073ab55DbView on Etherscan
DAOGovernor Implementation0x2F81fb483fD1B578d16d41e92c62A365b4b04081View on Etherscan
Example DAO on Sepolia:
ContractAddressExplorer Link
DAOToken (Proxy)0x2F524705E04aFa3b450a8C60f04975630B6deff4View on Etherscan
DAOGovernor (Proxy)0x707e6c8d2C52C16eA4F93e41932b11e34814B4B0View on Etherscan
TimelockController (Treasury)0x2cA78756658e85DC5F175363553225881e8537FCView on Etherscan

​
Deterministic Deployment Details

All CreateDAO v2 contracts use CREATE2 for deterministic deployment, ensuring consistent addresses across networks. CREATE2 Configuration: 
CREATE2 Deployer: 0x4e59b44847b379578588920cA78FbF26c0B4956C
Salt: CreateDAO_Production_v2_0_0
Salt Hash: 0x86e878d0db536a6fd426beb56994c299552f4885e0000a9bb0b08f46860e1fdb
Init Code Hash: 0xb88b2130abbf8e7570a958fcdc98f4143b26f2bd1d7ad95c56b62f31350f8485
This means the DAOFactory address is identical across all supported chains when deployed with the same salt.

​
Verifying Contract Authenticity

​
Method 1: Check Factory Address

The official DAOFactory address is: 
0xd141662F4b788F28B2a0769a6d3f243D046B571f
Always verify you’re interacting with this address on the correct network.

​
Method 2: Query Implementation Addresses

You can verify the implementation addresses programmatically: 
import { ethers } from 'ethers';

const factory = await ethers.getContractAt(
    "DAOFactory",
    "0xd141662F4b788F28B2a0769a6d3f243D046B571f"
);

const [tokenImpl, governorImpl] = await factory.getImplementations();

console.log("Token Implementation:", tokenImpl);
console.log("Governor Implementation:", governorImpl);
Expected results:
  • Token: 0xfAAB628eddeEC6093CCdB5288b865a8073ab55Db
  • Governor: 0x2F81fb483fD1B578d16d41e92c62A365b4b04081

​
Method 3: Verify Source Code

All contracts have verified source code on block explorers:
  1. Visit the contract on the explorer
  2. Click the “Contract” tab
  3. Verify source code is visible and matches the GitHub repository

​
Understanding Your DAO’s Contracts

When you create a DAO using the factory, you get three contracts:

​
1. DAOToken (EIP-1167 Proxy)

  • Type: Minimal proxy (45 bytes)
  • Delegates to: DAOToken Implementation
  • Functionality: ERC20 governance token with auto-delegation
  • Your Instance: Each DAO gets its own isolated proxy

​
2. DAOGovernor (EIP-1167 Proxy)

  • Type: Minimal proxy (45 bytes)
  • Delegates to: DAOGovernor Implementation
  • Functionality: Governance with OpenZeppelin extensions + Manager role
  • Your Instance: Each DAO gets its own isolated proxy

​
3. TimelockController (Full Contract)

  • Type: Full contract deployment (not a proxy)
  • Functionality: Treasury + execution delay
  • Holds: 99% of your DAO’s token supply

​
Integration Examples

​
Connect to Factory

import { createPublicClient, http } from 'viem';
import { base } from 'viem/chains';

const client = createPublicClient({
  chain: base,
  transport: http()
});

const FACTORY_ADDRESS = '0xd141662F4b788F28B2a0769a6d3f243D046B571f';

// Read DAO count
const daoCount = await client.readContract({
  address: FACTORY_ADDRESS,
  abi: DAOFactoryABI,
  functionName: 'getDAOCount'
});

​
Verify Manager

// Check who the current manager is for a DAO
const managerAddress = await client.readContract({
  address: GOVERNOR_ADDRESS,
  abi: DAOGovernorABI,
  functionName: 'manager'
});

console.log("Current Manager:", managerAddress);

​
Network Information

​
Base (Mainnet)

  • Chain ID: 8453
  • RPC: https://mainnet.base.org
  • Explorer: https://basescan.org
  • Currency: ETH
  • Type: L2 (Optimistic Rollup)

​
Sepolia (Testnet)

​
Coming Soon

CreateDAO v2 will expand to additional networks. Stay tuned for announcements on:
  • Polygon
  • Arbitrum
  • Optimism
  • Other EVM-compatible chains
Follow us on Twitter for deployment announcements.

​
Security Notice

Always verify contract addresses from official CreateDAO sources before interacting with them. Do not trust addresses provided by third parties.
If you discover a contract claiming to be CreateDAO but not listed here, please report it immediately:

​
Source Code & Verification

All contracts are verified on their respective block explorers with matching source code from the GitHub repository.