• Open now · 50 briefs
    Get paid in DFR to help build this forum
    DAOForum runs like a real DAO — so anyone can contribute, not just watch. Pick one of 50 open topics from the Curated Launch Library, write it, and an accepted thread pays 2,000–4,000 DFR straight from the on-chain treasury. The DFR is yours — hold it or sell it. No fee to claim, no wallet to connect — you only share an address at the end so the treasury can pay you. Do the real thing, and if you're good, become part of the team.

DAO creation and operations

Mimah

Member
Good governance is one of the most important parts of running a successful DAO. Giving token holders voting rights is a good start, but it doesn't automatically make a DAO secure or decentralized.
‎
‎Without proper rules, a small group of holders could control decisions, malicious proposals could put treasury funds at risk, and important security updates could be delayed.
‎
‎There are four areas every DAO should pay attention to: quorum, timelocks, voting periods, and Security Councils.
‎
‎1. Quorum: Making Sure Enough People Participate
‎
‎Quorum is the minimum voting power required for a proposal to be valid.
‎
‎For example, if a DAO has 10 million eligible governance tokens and sets its quorum at 10%, at least 1 million tokens must participate for a proposal to meet quorum.
‎
‎But quorum and approval are two different things.
‎
· ‎Quorum determines whether enough people participated.
· ‎Approval determines whether enough voters supported the proposal.
‎
‎A proposal can receive 80% support from participating voters and still fail if it doesn't reach quorum.
‎
‎DAOs should avoid setting quorum too high or too low. A very low threshold makes it easier for a small group to push through decisions, while an extremely high threshold can prevent useful proposals from passing.
‎
‎The best approach is to look at actual voter participation and adjust the threshold accordingly.
‎
‎Compound's governance system is a useful example of how token-based voting and delegation can work.
‎
‎Reference: https://docs.compound.finance/v2/governance/
‎
‎2. Timelocks: Giving the Community Time to React
‎
‎A timelock introduces a waiting period between proposal approval and execution.
‎
‎This is important because a proposal can pass and still turn out to be dangerous.
‎
‎Imagine a DAO managing $20 million. A malicious proposal gets approved to transfer a large amount of treasury funds to an unknown wallet.
‎
‎If execution happens immediately, the community might not have enough time to respond.
‎
‎With a timelock, execution is delayed, giving members an opportunity to review the transaction and raise concerns.
‎
‎However, timelocks are not a complete security solution. Attackers may still exploit governance control, manipulate proposal settings, or try to reduce the delay before executing a harmful transaction.
‎
‎Some important safeguards include:
‎
· ‎Preventing unauthorized changes to timelock settings.
· ‎Reviewing every transaction included in a proposal.
· ‎Restricting proposer and executor permissions.
· ‎Having an emergency cancellation process.
· ‎Monitoring proposals before execution.
‎
‎For example, a DAO could use a 48–72-hour delay for ordinary changes and a longer delay for major treasury transfers or contract upgrades.
‎
‎OpenZeppelin Governor provides useful tools for implementing governance systems with voting and timelock functionality.
‎
‎Reference: https://docs.openzeppelin.com/contracts/5.x/governance
‎
‎3. Voting Periods Should Reflect Treasury Risk
‎
‎Not every proposal deserves the same voting period.
‎
‎A minor community decision may not need two weeks of discussion, but a proposal involving millions of dollars should give members enough time to understand what they are approving.
‎
‎Consider two DAOs:
‎
· ‎DAO A manages $100,000.
· ‎DAO B manages $50 million.
‎
‎A proposal to spend $10,000 has very different consequences for these organizations.
‎
‎The larger DAO should generally have stronger review procedures, especially when proposals involve treasury transfers, protocol upgrades, or changes to administrative permissions.
‎
‎One possible voting structure is:
‎
· ‎Routine proposals: 3–5 days.
· ‎General financial proposals: 5–7 days.
· ‎Major treasury decisions: 7–14 days.
· ‎Critical protocol upgrades: 7–14 days or longer.
‎
‎These are suggested ranges, not fixed industry standards.
‎
‎DAOs should also consider voter participation, community size, and how complicated a proposal is.
‎
‎The goal is to give people enough time to make informed decisions without making governance unnecessarily slow.
‎
‎4. Security Councils: An Extra Layer of Protection
‎
‎Even with good voting rules, emergencies can happen.
‎
‎A smart contract vulnerability or active exploit may require action faster than ordinary governance can provide.
‎
‎This is where a Security Council becomes useful.
‎
‎A Security Council is a group of trusted members responsible for responding to critical security situations.
‎
‎One common arrangement is a 7-member multisignature council where at least 4 members must approve an emergency action.
‎
‎This prevents one person from having complete control.
‎
‎Security Councils may be given limited powers to pause vulnerable functions or respond to specific threats.
‎
‎However, they should not have unlimited authority over DAO funds or ordinary governance decisions.
‎
‎Some important safeguards include:
‎
· ‎Clear limits on emergency powers.
· ‎Multiple signatures before action.
· ‎Regular review of council membership.
· ‎Transparent reporting after emergency interventions.
· ‎A community process for replacing members.
‎
‎Optimism and Arbitrum both provide useful examples of how Security Councils can fit into larger governance structures.
‎
‎Optimism: https://gov.optimism.io/
‎
‎Arbitrum: https://docs.arbitrum.foundation/
‎
‎5. Bringing Everything Together
‎
‎These four mechanisms work best when they support each other.
‎
‎For example, imagine a DAO with a $25 million treasury.
‎
‎It could adopt the following starting configuration:
‎
‎
‎These figures are examples, not universal recommendations. The DAO should adjust them based on token distribution, participation, and its security requirements.
‎
‎The important thing is to avoid relying on just one security measure.
‎
‎A high quorum doesn't prevent every attack. A timelock doesn't guarantee that malicious proposals will be stopped. And a Security Council should never become an excuse to remove the community from decision-making.
‎
‎Final Thoughts
‎
‎Good DAO governance is about finding the right balance between community participation, security, and efficiency.
‎
‎Quorum makes sure enough voting power participates. Timelocks give members time to review approved decisions. Appropriate voting periods make room for proper discussion, while Security Councils provide an emergency response mechanism.
‎
‎No governance model is perfect, but combining these protections can make a DAO much harder to manipulate.
‎
‎Ultimately, decentralization should not just mean allowing everyone to vote. It should also mean making sure that power is properly distributed, decisions are transparent, and the community's assets are protected.
‎
‎What do you think matters most for a DAO managing millions of dollars: higher quorum, longer timelocks, or a stronger Security Council?
‎
‎Sources
‎
1. ‎Compound Governance: https://docs.compound.finance/v2/governance/
2. ‎OpenZeppelin Governor: https://docs.openzeppelin.com/contracts/5.x/governance
3. ‎Optimism Governance: https://gov.optimism.io/
4. ‎Arbitrum Governance: https://docs.arbitrum.foundation/
‎
 
Good governance is one of the most important parts of running a successful DAO. Giving token holders voting rights is a good start, but it doesn't automatically make a DAO secure or decentralized.
‎
‎Without proper rules, a small group of holders could control decisions, malicious proposals could put treasury funds at risk, and important security updates could be delayed.
‎
‎There are four areas every DAO should pay attention to: quorum, timelocks, voting periods, and Security Councils.
‎
‎1. Quorum: Making Sure Enough People Participate
‎
‎Quorum is the minimum voting power required for a proposal to be valid.
‎
‎For example, if a DAO has 10 million eligible governance tokens and sets its quorum at 10%, at least 1 million tokens must participate for a proposal to meet quorum.
‎
‎But quorum and approval are two different things.
‎
· ‎Quorum determines whether enough people participated.
· ‎Approval determines whether enough voters supported the proposal.
‎
‎A proposal can receive 80% support from participating voters and still fail if it doesn't reach quorum.
‎
‎DAOs should avoid setting quorum too high or too low. A very low threshold makes it easier for a small group to push through decisions, while an extremely high threshold can prevent useful proposals from passing.
‎
‎The best approach is to look at actual voter participation and adjust the threshold accordingly.
‎
‎Compound's governance system is a useful example of how token-based voting and delegation can work.
‎
‎Reference: https://docs.compound.finance/v2/governance/
‎
‎2. Timelocks: Giving the Community Time to React
‎
‎A timelock introduces a waiting period between proposal approval and execution.
‎
‎This is important because a proposal can pass and still turn out to be dangerous.
‎
‎Imagine a DAO managing $20 million. A malicious proposal gets approved to transfer a large amount of treasury funds to an unknown wallet.
‎
‎If execution happens immediately, the community might not have enough time to respond.
‎
‎With a timelock, execution is delayed, giving members an opportunity to review the transaction and raise concerns.
‎
‎However, timelocks are not a complete security solution. Attackers may still exploit governance control, manipulate proposal settings, or try to reduce the delay before executing a harmful transaction.
‎
‎Some important safeguards include:
‎
· ‎Preventing unauthorized changes to timelock settings.
· ‎Reviewing every transaction included in a proposal.
· ‎Restricting proposer and executor permissions.
· ‎Having an emergency cancellation process.
· ‎Monitoring proposals before execution.
‎
‎For example, a DAO could use a 48–72-hour delay for ordinary changes and a longer delay for major treasury transfers or contract upgrades.
‎
‎OpenZeppelin Governor provides useful tools for implementing governance systems with voting and timelock functionality.
‎
‎Reference: https://docs.openzeppelin.com/contracts/5.x/governance
‎
‎3. Voting Periods Should Reflect Treasury Risk
‎
‎Not every proposal deserves the same voting period.
‎
‎A minor community decision may not need two weeks of discussion, but a proposal involving millions of dollars should give members enough time to understand what they are approving.
‎
‎Consider two DAOs:
‎
· ‎DAO A manages $100,000.
· ‎DAO B manages $50 million.
‎
‎A proposal to spend $10,000 has very different consequences for these organizations.
‎
‎The larger DAO should generally have stronger review procedures, especially when proposals involve treasury transfers, protocol upgrades, or changes to administrative permissions.
‎
‎One possible voting structure is:
‎
· ‎Routine proposals: 3–5 days.
· ‎General financial proposals: 5–7 days.
· ‎Major treasury decisions: 7–14 days.
· ‎Critical protocol upgrades: 7–14 days or longer.
‎
‎These are suggested ranges, not fixed industry standards.
‎
‎DAOs should also consider voter participation, community size, and how complicated a proposal is.
‎
‎The goal is to give people enough time to make informed decisions without making governance unnecessarily slow.
‎
‎4. Security Councils: An Extra Layer of Protection
‎
‎Even with good voting rules, emergencies can happen.
‎
‎A smart contract vulnerability or active exploit may require action faster than ordinary governance can provide.
‎
‎This is where a Security Council becomes useful.
‎
‎A Security Council is a group of trusted members responsible for responding to critical security situations.
‎
‎One common arrangement is a 7-member multisignature council where at least 4 members must approve an emergency action.
‎
‎This prevents one person from having complete control.
‎
‎Security Councils may be given limited powers to pause vulnerable functions or respond to specific threats.
‎
‎However, they should not have unlimited authority over DAO funds or ordinary governance decisions.
‎
‎Some important safeguards include:
‎
· ‎Clear limits on emergency powers.
· ‎Multiple signatures before action.
· ‎Regular review of council membership.
· ‎Transparent reporting after emergency interventions.
· ‎A community process for replacing members.
‎
‎Optimism and Arbitrum both provide useful examples of how Security Councils can fit into larger governance structures.
‎
‎Optimism: https://gov.optimism.io/
‎
‎Arbitrum: https://docs.arbitrum.foundation/
‎
‎5. Bringing Everything Together
‎
‎These four mechanisms work best when they support each other.
‎
‎For example, imagine a DAO with a $25 million treasury.
‎
‎It could adopt the following starting configuration:
‎
‎
‎These figures are examples, not universal recommendations. The DAO should adjust them based on token distribution, participation, and its security requirements.
‎
‎The important thing is to avoid relying on just one security measure.
‎
‎A high quorum doesn't prevent every attack. A timelock doesn't guarantee that malicious proposals will be stopped. And a Security Council should never become an excuse to remove the community from decision-making.
‎
‎Final Thoughts
‎
‎Good DAO governance is about finding the right balance between community participation, security, and efficiency.
‎
‎Quorum makes sure enough voting power participates. Timelocks give members time to review approved decisions. Appropriate voting periods make room for proper discussion, while Security Councils provide an emergency response mechanism.
‎
‎No governance model is perfect, but combining these protections can make a DAO much harder to manipulate.
‎
‎Ultimately, decentralization should not just mean allowing everyone to vote. It should also mean making sure that power is properly distributed, decisions are transparent, and the community's assets are protected.
‎
‎What do you think matters most for a DAO managing millions of dollars: higher quorum, longer timelocks, or a stronger Security Council?
‎
‎Sources
‎
1. ‎Compound Governance: https://docs.compound.finance/v2/governance/
2. ‎OpenZeppelin Governor: https://docs.openzeppelin.com/contracts/5.x/governance
3. ‎Optimism Governance: https://gov.optimism.io/
4. ‎Arbitrum Governance: https://docs.arbitrum.foundation/
‎

‎
‎Running a DAO is not just about giving token holders the ability to vote. A good governance system must also make sure that decisions are fair, transparent, and protected from manipulation.
‎
‎Some DAOs struggle with low voter participation, while others face problems caused by large token holders having too much influence. There are also risks involving malicious proposals, treasury withdrawals, and compromised governance permissions.
‎
‎These problems show why governance rules need to be carefully designed from the beginning.
‎
‎Four important areas deserve particular attention: quorum calculations, timelock security, voting periods based on treasury risk, and Security Councils.
‎
‎Looking at projects such as Compound, Optimism, and Arbitrum can help us understand how different governance mechanisms work and what other DAOs can learn from them.
‎
‎1. Quorum Mathematics: How Much Voting Power Is Enough?
‎
‎Quorum is the minimum amount of voting power required for a proposal to be considered valid.
‎
‎It is important because a proposal should not automatically pass just because a few active members support it while most of the community has not participated.
‎
‎Let's use a simple example.
‎
‎Imagine a DAO has 10 million eligible governance tokens and sets its quorum at 10%.
‎
‎The calculation is:
‎
‎Quorum = Eligible voting supply × Quorum percentage
‎
‎Therefore:
‎
‎10,000,000 × 10% = 1,000,000 tokens.
‎
‎This means at least 1 million tokens must participate for the proposal to meet quorum.
‎
‎If only 700,000 tokens participate, the proposal fails to reach quorum, even if almost everyone who voted supported it.
‎
‎However, quorum is not the same as the approval threshold. Quorum measures participation, while the approval threshold measures support.
‎
‎Understanding quorum and approval with an example
‎
‎Suppose a proposal receives the following votes:
‎
· ‎For: 800,000 tokens.
· ‎Against: 300,000 tokens.
· ‎Abstain: 100,000 tokens.
‎
‎Total participation is:
‎
‎800,000 + 300,000 + 100,000 = 1,200,000 tokens.
‎
‎Since the quorum requirement is 1 million tokens, the proposal reaches quorum.
‎
‎If the approval requirement is more than 50% of For and Against votes, the calculation becomes:
‎
‎800,000 ÷ (800,000 + 300,000) × 100 = 72.73%.
‎
‎The proposal therefore passes the majority requirement, assuming the Governor uses this counting method.
‎
‎Notice that abstentions count toward participation in this example but do not count as support or opposition.
‎
‎This is an important distinction because different governance contracts can use different vote-counting rules.
‎
‎Fixed quorum versus dynamic quorum
‎
‎There are two approaches worth understanding.
‎
‎Fixed quorum: The DAO establishes a specific participation threshold that remains unchanged until governance formally updates it.
‎
‎For example, a DAO might require 10% of eligible voting power to participate in every standard proposal.
‎
‎This approach is simple and predictable, but it can become unsuitable when voter participation or token distribution changes significantly.
‎
‎Dynamic quorum: The required participation threshold adjusts according to predetermined rules.
‎
‎For example, a DAO could use historical participation to influence its quorum requirement, subject to minimum and maximum limits.
‎
‎This can make governance more adaptable, although it also introduces additional complexity.
‎
‎What happens when token supply changes?
‎
‎Suppose a DAO initially has 10 million eligible tokens and requires 10% quorum.
‎
‎The requirement is 1 million tokens.
‎
‎Later, eligible voting supply increases to 15 million tokens.
‎
‎If quorum remains at 10%, the new requirement becomes:
‎
‎15,000,000 × 10% = 1,500,000 tokens.
‎
‎This shows why DAOs need to monitor their eligible voting supply and understand how their contracts calculate quorum.
‎
‎The calculation should also account for the actual voting system. Some Governors use a quorum based on historical token supply at a particular block, while others use different mechanisms.
‎
‎Choosing the right quorum
‎
‎A quorum that is too low can make governance vulnerable to a small group of active voters.
‎
‎A quorum that is too high can make it difficult for legitimate proposals to pass.
‎
‎For example, if average participation is around 12%, setting quorum at 25% could cause repeated failures.
‎
‎On the other hand, setting it at 1% may provide insufficient protection against decisions made with very little community participation.
‎
‎The best approach is to study voter participation, token distribution, and delegation patterns before choosing a threshold.
‎
‎Compound's governance documentation is a useful reference for understanding token-based voting, delegation, and proposal processes.
‎
‎Source: https://docs.compound.finance/v2/governance/
‎
‎2. Timelocks and the Attacks DAOs Should Watch Out For
‎
‎A timelock is a mechanism that delays the execution of an approved proposal.
‎
‎Instead of executing a transaction immediately after voting, the DAO schedules it to happen after a waiting period.
‎
‎This gives token holders and security researchers time to inspect the approved changes.
‎
‎For example, imagine a DAO managing $30 million in treasury assets. A proposal passes that would transfer $5 million to an external address.
‎
‎With no execution delay, the funds could be transferred before most members even notice what happened.
‎
‎A timelock creates an opportunity to identify suspicious activity and use available emergency procedures.
‎
‎However, timelocks are not perfect. There are several attack vectors DAOs should understand.
‎
‎Governance capture
‎
‎An attacker may acquire or control enough voting power to influence or pass a malicious proposal.
‎
‎The proposal could authorize an unauthorized treasury transfer or introduce a harmful smart contract upgrade.
‎
‎A timelock delays execution, but it does not automatically reject the proposal.
‎
‎DAOs should monitor unusual voting activity, large delegation changes, and sudden increases in voting power.
‎
‎Timelock manipulation
‎
‎Another risk is an attempt to reduce the timelock duration through governance.
‎
‎For example, imagine a DAO normally requires a seven-day delay before executing major upgrades.
‎
‎A malicious proposal could attempt to reduce that delay to a few minutes, making it easier to execute another dangerous transaction.
‎
‎One way to reduce this risk is to establish minimum delay requirements and additional protections around changes to critical governance parameters.
‎
‎Malicious proposal bundling
‎
‎Some proposals contain multiple transactions.
‎
‎An attacker could hide a dangerous permission change inside a proposal that otherwise appears harmless.
‎
‎For example, a proposal might request a routine protocol update while also granting an external wallet administrative permissions.
‎
‎This is why every transaction within a proposal should be reviewed, not just its title or summary.
‎
‎Compromised execution permissions
‎
‎If an attacker gains control of an authorized proposer or executor, they may attempt to schedule or execute unauthorized operations.
‎
‎DAOs should use restricted permissions, secure administrative keys, and monitoring systems to identify unusual activity.
‎
‎Choosing a reasonable timelock
‎
‎The delay should depend on the risk and consequences of the action.
‎
‎An illustrative structure could be:
‎
· ‎Minor parameter changes: 24–48 hours.
· ‎Regular protocol changes: 48–72 hours.
· ‎Major treasury transfers: 3–7 days.
· ‎Critical contract upgrades: 7–14 days.
‎
‎These are suggested policy ranges, not universal requirements.
‎
‎OpenZeppelin Governor provides useful tools for implementing voting and timelock functionality in smart contract governance.
‎
‎Source: https://docs.openzeppelin.com/contracts/5.x/governance
‎
‎3. Voting Periods Should Reflect Treasury Size and Risk
‎
‎Voting periods determine how long members have to review and vote on a proposal.
‎
‎A short voting period can exclude people who need more time to understand a decision. An unnecessarily long period can delay important changes and create governance fatigue.
‎
‎Treasury size is one factor worth considering.
‎
‎Imagine two DAOs:
‎
‎DAO A manages $200,000.
‎
‎DAO B manages $50 million.
‎
‎Both receive a proposal to spend $100,000.
‎
‎For DAO A, that represents 50% of its treasury.
‎
‎For DAO B, it represents only 0.2%.
‎
‎Although the requested amount is identical, the consequences are very different.
‎
‎DAO A should be particularly careful because the proposal could significantly affect its financial position.
‎
‎This is why voting periods should consider both the amount involved and the percentage of treasury being committed.
‎
‎Suggested voting periods
‎
‎A DAO could start with the following structure:
‎
‎
‎These are illustrative recommendations, not official settings used by the projects mentioned in this guide.
‎
‎Why short voting periods can be risky
‎
‎Not every token holder checks governance platforms daily.
‎
‎A proposal that closes after 24 hours could easily go unnoticed by many community members.
‎
‎Short periods can also make it difficult for delegates to investigate technical details, especially when a proposal involves smart contract changes.
‎
‎For major financial decisions, the community should have enough time to ask questions, examine the proposal, and understand the consequences.
‎
‎Why longer periods are not always better
‎
‎Longer voting periods also have disadvantages.
‎
‎Security updates may be delayed, market conditions may change, and members may lose interest in proposals that remain open for too long.
‎
‎The goal is not to make every vote last two weeks.
‎
‎It is to match the review period to the importance of the decision.
‎
‎A routine administrative change does not need the same level of review as a proposal involving millions of dollars or a major protocol upgrade.
‎
‎4. Security Councils: Protecting DAOs During Emergencies
‎
‎Even a well-designed governance system can face unexpected security problems.
‎
‎A smart contract exploit, compromised administrative key, or vulnerability in a bridge may require immediate attention.
‎
‎Ordinary governance voting may be too slow in these situations.
‎
‎This is where a Security Council can help.
‎
‎A Security Council is a group of trusted members given specific responsibilities for responding to critical security incidents.
‎
‎One common arrangement is a 7-member multisignature council requiring at least 4 approvals before an emergency action can be taken.
‎
‎This reduces the risk of one individual having complete control.
‎
‎Common Security Council patterns
‎
‎Multisignature council
‎
‎Several members hold separate signing keys, and a minimum number of approvals is required before an action can execute.
‎
‎For example, a 4-of-7 arrangement means four council members must approve a transaction.
‎
‎It offers shared responsibility, although collusion and compromised keys remain possible risks.
‎
‎Guardian-based emergency response
‎
‎A guardian system gives designated participants limited powers to respond to specific security threats.
‎
‎For example, guardians may be permitted to pause vulnerable protocol functions while the community investigates an incident.
‎
‎Their authority should be clearly restricted.
‎
‎Community-elected council
‎
‎In this structure, DAO members elect Security Council participants through governance.
‎
‎Members can serve fixed terms and be replaced through an established voting process.
‎
‎This improves accountability because the council does not become a permanent group with unlimited authority.
‎
‎Lessons from Optimism and Arbitrum
‎
‎Optimism provides an interesting example of governance involving different community participation structures.
‎
‎The Optimism Collective includes the Token House and Citizens' House, which have different roles in its governance framework. Its Security Council also forms part of its security architecture.
‎
‎The broader lesson is that specialized security responsibilities can exist alongside community governance.
‎
‎Arbitrum also uses a Security Council as part of its DAO governance and security arrangements.
‎
‎Its governance documentation provides information about the relationship between the DAO and its security mechanisms.
‎
‎Both examples demonstrate why emergency security responsibilities need to be defined rather than left to informal arrangements.
‎
‎References:
‎
‎Optimism: https://gov.optimism.io/
‎
‎Arbitrum: https://docs.arbitrum.foundation/
‎
‎What makes a Security Council trustworthy?
‎
‎A Security Council should not become more powerful than the DAO itself.
‎
‎Some important safeguards include:
‎
· ‎Require multiple signatures for emergency actions.
· ‎Clearly document the council's permitted actions.
· ‎Establish transparent appointment and removal procedures.
· ‎Require members to disclose conflicts of interest.
· ‎Publish explanations after emergency interventions when safe.
· ‎Review council activity regularly.
· ‎Test emergency procedures before an actual incident happens.
‎
‎A council should be able to protect the protocol without taking over ordinary community decisions.
‎
‎5. How These Mechanisms Work Together
‎
‎The four governance mechanisms should support one another.
‎
‎Consider a DAO managing a $25 million treasury with 20 million eligible governance tokens.
‎
‎It could begin with the following example configuration:
‎
‎
‎Now imagine someone proposes a $4 million ecosystem development fund.
‎
‎First, the proposal is published with its budget, recipient information, milestones, and payment conditions.
‎
‎Community members and delegates review the details before voting begins.
‎
‎During the 14-day voting period, eligible token holders cast their votes.
‎
‎If participation reaches the 2 million token quorum and the proposal satisfies the approval requirement, it moves into the timelock.
‎
‎After the seven-day delay, the authorized executor can carry out the approved transaction.
‎
‎The DAO should then monitor the fund's use and require progress reports from the recipient.
‎
‎This process does not eliminate every risk, but it provides several opportunities to identify problems before and after funds are transferred.
‎
‎6. Common Governance Mistakes to Avoid
‎
‎There are a few mistakes that DAOs should be careful about.
‎
‎Setting quorum without studying participation: Copying another DAO's quorum percentage without understanding your own voter activity can create problems.
‎
‎Ignoring token concentration: A DAO may have thousands of token holders, but a small number of wallets might control most voting power.
‎
‎Treating timelocks as complete protection: A delay is useful, but it cannot guarantee that a malicious proposal will be stopped.
‎
‎Giving Security Councils unlimited authority: Emergency powers should remain limited and accountable.
‎
‎Using the same voting period for every proposal: Different decisions carry different levels of financial and technical risk.
‎
‎Failing to test emergency procedures: Security arrangements should be tested before an actual exploit occurs.
‎
‎These issues are worth reviewing regularly, especially as a DAO grows and its treasury becomes larger.
‎
‎7. Final Thoughts
‎
‎Good DAO governance is about more than voting. It is about making sure that decisions are legitimate, participation is meaningful, and the community's assets are protected.
‎
‎Quorum helps prevent decisions from being made with insufficient participation. Timelocks give the community time to inspect approved transactions. Appropriate voting periods allow members to understand important proposals, while Security Councils provide an additional layer of protection during emergencies.
‎
‎None of these mechanisms is perfect on its own.
‎
‎A DAO with a strong quorum can still experience governance capture. A long timelock cannot automatically reverse a malicious transaction. Even a well-organized Security Council needs clear limits and accountability.
‎
‎The best approach is to combine these protections and review them as the DAO develops.
‎
‎At the end of the day, decentralization should not only be about who gets to vote. It should also be about how power is distributed, how decisions are executed, and how the community is protected.
‎
‎What would you prioritize if your DAO suddenly grew to manage $50 million: higher quorum, longer timelocks, or a stronger Security Council?
‎
‎Sources and Further Reading
‎
1. ‎Compound Governance: https://docs.compound.finance/v2/governance/
2. ‎OpenZeppelin Governor: https://docs.openzeppelin.com/contracts/5.x/governance
3. ‎Optimism Governance: https://gov.optimism.io/
4. ‎Arbitrum Governance: https://docs.arbitrum.foundation/

@Diornov
‎
‎
‎
 
Back
Top