Design & Implement DAO Governance Frameworks

DAO Governance Framework Expert is a skill for designing, implementing, and optimizing decentralized governance systems: voting mechanisms, tokenomics, proposal management, execution strategy, and the technical architecture behind them.

Its voting systems cover quadratic voting (reduces whale dominance by requiring a quadratic token commitment), conviction voting (time-weighted voting that rewards sustained commitment), delegated voting (token holders delegate to trusted representatives), and multi-token voting (combining governance, utility, and reputation tokens for nuanced decisions). Its proposal lifecycle runs through five phases: ideation (community discussion and initial drafting), formal submission (technical review and formatting requirements), a voting period (a defined timeframe with quorum requirements), execution (automatic or manual implementation), and post-implementation review (monitoring and outcome evaluation).

For smart-contract architecture it covers an OpenZeppelin-based Governor contract (with quadratic-scaled voting power) and a multisig treasury requiring a set number of approvals before executing a transaction. Advanced mechanisms include rage-quit protection (a waiting period after which a member can burn their tokens for a proportional treasury share) and off-chain reputation-based governance, where voting power blends token balance, a reputation score, and staking duration, and reputation is adjusted up or down based on whether a member's vote matched the proposal's outcome. Its tokenomics patterns cover vesting schedules (total amount, start, duration, and cliff) and dynamic monthly token distribution weighted across measurable contributions - code commits, proposals submitted, voting participation, and community engagement, each capped and weighted differently.

Use it when designing or hardening a DAO's governance - choosing a voting mechanism, structuring the proposal lifecycle, securing the treasury, or measuring governance health - rather than a simple single-signer admin setup. Its own progressive-decentralization framework (core-team control, hybrid governance, full community control, then immutable governance) implies this is for a DAO actually moving toward decentralization, not one that intends to stay centrally controlled; it explicitly recommends timelocks, multisig, and emergency-pause mechanisms precisely because a fully decentralized, immutable system removes the ability to intervene later.

Input is the DAO's governance requirements: token model, desired voting mechanism, treasury structure, and decentralization roadmap. Output is smart-contract patterns (Governor, treasury multisig, rage-quit, vesting), an off-chain reputation and reward-calculation model, and a governance health dashboard tracking measurable signals:

// Governance health metrics dashboard
const governanceMetrics = {
  participationRate: votersCount / totalTokenHolders,
  proposalSuccessRate: passedProposals / totalProposals,
  averageVotingPower: totalVotesCast / votersCount,
  treasuryUtilization: spentFunds / totalTreasury,
  decentralizationIndex: calculateHerfindahlIndex(votingPowerDistribution)
};

function assessGovernanceHealth() {
  return {
    participation: governanceMetrics.participationRate > 0.15 ? 'Healthy' : 'Concerning',
    engagement: governanceMetrics.proposalSuccessRate > 0.4 ? 'Active' : 'Stagnant',
    decentralization: governanceMetrics.decentralizationIndex < 0.3 ? 'Decentralized' : 'Concentrated'
  };
}

Its smart-contract patterns build on OpenZeppelin's Governor, GovernorVotes, GovernorVotesQuorumFraction, and GovernorTimelockControl modules in Solidity, with off-chain reputation and reward calculations implemented in JavaScript.

DAO founders, governance engineers, and protocol teams designing or auditing decentralized governance - voting mechanisms, treasury security, tokenomics, and progressive decentralization - who want concrete, measurable patterns rather than an ungoverned admin key.