Development of Nouns-style DAO: Auctions, Voting, Fork

Full-cycle development of Nouns-style DAO

We develop Nouns-style DAOs from scratch. A Nouns-style DAO features daily auctions, on-chain voting, and a fork mechanism. Several years ago Nouns DAO reshaped the perception of NFTs and DAOs: one Noun auctioned daily, one vote per Noun. No pre-mine, no whitelist—only a transparent on-chain system. The treasury exceeds 30,000 ETH and operates continuously for years. This is not just a mechanic but a design pattern we reproduce for Lil Nouns, Gnars, Purple, and other projects.

Our team has delivered over 100 blockchain projects, including several DAO ecosystems. We offer a full cycle: from design to post-launch support. On one project, we reduced gas consumption by 30% compared to the base implementation, saving thousands of dollars in ETH for active participants. Bundling services can cut audit costs by up to $5,000.

How does the daily auction work?

The core is the AuctionHouse contract. Every 24 hours a new NFT is listed. Bids are in ETH; the latest bidder outbids the previous one and gets a refund. If a bid is placed within the last 15 minutes, the auction extends—a sniping protection. We use exactly this mechanism with a timeBuffer.

function createBid(uint256 nounId) external payable nonReentrant {
    require(block.timestamp < _auction.endTime, "Auction expired");
    require(msg.value >= reservePrice, "Below reserve");
    require(msg.value >= _auction.amount + ((_auction.amount * minBidIncrementPercentage) / 100), "Low increment");
    // Return previous bidder
    _safeTransferETHWithFallback(lastBidder, _auction.amount);
    // Update bid
    auction.amount = msg.value;
    auction.bidder = payable(msg.sender);
    // Extend if needed
    if (_auction.endTime - block.timestamp < timeBuffer) {
        auction.endTime = block.timestamp + timeBuffer;
    }
}

Why is on-chain artwork important?

All image layers are stored directly in the contract—no IPFS, no centralized server. SVG generation happens on-chain, ensuring the NFT remains available as long as Ethereum exists. We use the NounsDescriptor approach with RLE byte compression to minimize gas. The reserve price is typically set at 0.001 ETH, and the timeBuffer at 15 minutes.

Key system components

• NounsToken (ERC-721 + checkpoint voting): Each NFT is one vote. Instead of standard ERC20Votes, we implement a custom checkpoint system storing voting history.
• AuctionHouse: The auction mechanics described above.
• Governor: Voting with an objection period: after voting ends, there is a 48-hour window where only "no" votes are accepted. This prevents last-minute manipulation.
• Treasury (Timelock): Managed via governance.

Additionally: NounsDescriptor for on-chain SVG, NounsSeeder for random seed (we use Chainlink VRF for guaranteed unpredictability).

Technical gas details: Creating an NFT with on-chain artwork costs about 0.001 ETH at 50 gwei. An auction bid consumes roughly 100k gas. RLE compression reduces stored data size by 60%, cutting deployment cost by 40%. In our projects, we use Foundry—it runs tests 5 times faster than Hardhat, achieving 99% coverage.

How does the fork protect the minority?

If a major holder disagrees with a passed proposal, they can initiate a fork. Their tokens are escrowed, and once the threshold (e.g., 20% of total supply) is reached, a new DAO is created with a proportional share of the treasury. This is an alternative to the standard rage quit in Moloch-style DAOs.

What is included

• Parameter design: auction duration, reserve price, founder allocation, quorum, fork threshold.
• NFT contract with on-chain or IPFS artwork.
• Governance integration with fork mechanics.
• Frontend: auction page, NFT gallery, voting interface.
• Full test suite (Foundry) and security audit.
• Deployment and management documentation.
• One-month post-launch support.

We guarantee no reentrancy, flash loan attacks, or other vulnerabilities thanks to formal verification and fuzzing with Echidna.

Process

1. Analysis: Align parameters and requirements.
2. Design: Smart contract architecture.
3. Development: NFT contract and artwork descriptor.
4. Auction house implementation.
5. Governor setup with fork mechanics.
6. Testing: Unit + fork simulation + fuzzing.
7. Deployment and frontend.
8. Post-launch support.

Timelines and cost

Estimated timelines: 8 to 16 weeks, depending on artwork complexity and customization. Cost is calculated individually—based on contract volume, on-chain artwork needs, and frontend requirements. Contact us for a consultation—we will assess your project in one business day and provide a detailed plan.

Comparison with other approaches

From a community-building perspective, Nouns-style provides a daily touchpoint—the auction becomes an event, which is rare in other DAOs. Order development and get a ready-made ecosystem for your community.

DAO Development: Governance That Works

We have extensive experience in DAO development, having executed over 30 integrations of Governor, Safe, and Snapshot for protocols with TVL ranging from $1M to $500M. The problem is typical: the protocol is launched, liquidity exists, the token is distributed. The next step is handing control to the community. In practice, this means someone has to write contracts that prevent 5% of holders from draining the treasury through a single vote, while not locking legitimate upgrades for 18 months. The balance is nontrivial.

Why do most DAOs become oligarchies?

Typical scenario: fork OpenZeppelin Governor, deploy, launch Snapshot — and end up with a DAO effectively run by 3 addresses. The problem isn't the code but the tokenomics and parameters.

Quorum too high or too low. Compound set quorum at 400,000 COMP. With low turnout, proposals fail for months. With low quorum, one large holder can pass any question. The correct quorum depends on actual token distribution and average turnout, not a nice number. We analyze voting history, locked vs. circulating ratio, and select a dynamic quorum via GovernorVotesQuorumFraction.

Flash loan governance attack. Classic: attacker takes a flash loan, obtains voting power for one block, creates and passes a proposal. Protection: votingDelay of at least 1-2 blocks plus a snapshot at the proposal creation block, not at the voting block. OpenZeppelin's GovernorVotes handles the snapshot correctly, but if you write a custom contract, it's easy to miss. Beanstalk lost $182M due to lack of whitelist targets in the timelock — this case became the industry standard mistake.

Timelock without executor whitelist. If TimelockController does not restrict the list of allowed target contracts, an approved proposal can call any function. We always configure TimelockController with a whitelist of addresses and a minimum delay of 48 hours for protocols with TVL > $10M. For larger ones, 7 days, providing time to challenge via hard fork or multisig emergency.

On-chain governance architecture

Standard stack: OpenZeppelin Governor + TimelockController + ERC-20Votes (or ERC-721Votes for NFT-based governance). We use Foundry for development and testing — it allows forking mainnet and simulating attacks against the real state of contracts.

ERC-20Votes token
      │
      ▼
GovernorBravo / OZ Governor  ──→  TimelockController  ──→  Treasury / Protocol
      │
      ▼
  Snapshot (off-chain signaling)

Governor handles voting logic: propose, castVote, queue, execute. Timelock adds a delay between proposal approval and execution — a window for dissenters to exit. Delegated voting via ERC-20Votes is critical for protocols with many passive holders; without it, quorum is physically unreachable.

Snapshot + on-chain: hybrid model

Fully on-chain voting costs gas. For protocols with active communities, this means either high participation barriers or L2. Hybrid model: Snapshot for signaling votes (off-chain, gasless via EIP-712 signatures), on-chain only for execution. We prefer SafeSnap (Zodiac module from Gnosis) — the result is verified via Reality.eth (optimistic oracle) and automatically executed through Safe without a trusted party.

Multi-sig: Gnosis Safe as an operational layer

Most DAOs use Gnosis Safe for treasury. Standard configuration: M-of-N, where N is 7-9 signers from different time zones, M is 4-5. Fewer is unsafe. More is an operational nightmare for urgent transactions. Safe supports modules: Zodiac, Delay, Roles. Through the Roles module, you can grant a specific address the right to call only certain treasury functions — for example, only transfer up to a certain amount, without the right to delegatecall.

Important: Safe multisig and Governor are separate layers. Governor manages the protocol (upgrades, parameters). Safe manages the treasury (payments, grants). Mixing them into one contract is an architectural mistake that can cost millions.

How to protect a DAO from flash loan attacks?

We use multiple layers of protection. First, votingDelay of at least 2 blocks (OZ recommends 1, but we set 2 for extra safety). Second, the snapshot is taken at the proposal creation block, not the voting block — this blocks flash loan attacks because the loan is taken in the same block as voting. Third, GovernorPreventLateQuorum extends the voting period if quorum is reached in the last few blocks — without this extension, a large holder could wait until the end of the period and change the outcome with a single vote.

Governor Extensions: almost always needed

On-chain vs Off-chain voting: when to choose each

Choice depends on community budget and security requirements. For protocols with TVL > $50M, we recommend on-chain with L2 (Arbitrum, Optimism) — voting cost drops to $0.05-0.5.

Development process and parameter audit

Work starts not with code but with tokenomics: current token distribution, real turnout of similar protocols, list of operations that should require governance and those that should not. We analyze data via Dune and Nansen to determine realistic quorum and thresholds.

After parameterization: implementation of Governor based on OZ with custom extensions, integration with existing token (or deployment of a new one with ERC-20Votes), configuration of Safe multisig, setup of Snapshot space with correct strategy (often erc20-balance-of is insufficient — a delegation strategy is needed).

Testing includes simulation of governance attacks: flash loan quorum, proposal spam, malicious executor. Foundry allows forking mainnet and running attacks against real contract state. Deploying Governor without parameter audit is a standard mistake. Auditors look at code. But no one checks if a quorum of 10% of totalSupply is unreachable given the current locked/circulating ratio.

We guarantee that parameters are tuned to your community and provide a detailed report justifying every threshold. Experience shows that correct parameterization reduces governance attack risk by 80% (based on our data over 5 years of work).

What you will get in the end

• Smart contracts: Governor, Timelock, Token (ERC-20Votes/ERC-721Votes) with tests and documentation
• Configured Safe multisig with modules (Zodiac, Delay, Roles if needed)
• Snapshot space with custom voting strategy
• Governance parameter audit: quorum, voting period, delay, delegation mechanics
• Integration with existing protocol (treasury, staking, bridges)
• Team support and training (4 hours of consultation)
• Documentation on governance and emergency procedures

Timeline

Basic DAO system (Governor + Timelock + Safe + Snapshot) — from 3 to 6 weeks. With custom Zodiac modules, non-standard voting strategy, integration with existing protocol — from 6 to 12 weeks. Audit takes separately 2-4 weeks.

Contact us to audit your current configuration or order DAO development with security guarantees — we have completed over 50 such projects and know where the risks hide.