Quorum
Minimum participation required for a decision or action to be valid.
A quorum is the minimum level of participation required for a vote, meeting, consensus decision, or authorized action to be valid. It may be expressed as a number of members, a percentage of eligible voting power, or a threshold of signatures. Reaching quorum establishes sufficient participation, but does not necessarily mean the proposal passes.
In DAO governance, quorum often measures how much token voting power takes part in a proposal. For example, rules might require participation from at least four percent of eligible supply, followed by a simple majority of votes cast. Some systems count abstentions toward quorum while excluding them from the approval calculation. Others require a percentage of all eligible votes to support the proposal directly.
Quorum matters because decisions made by a tiny active group may not represent the broader community. A minimum threshold can protect treasuries, upgrades, and parameter changes from low-turnout capture. In blockchain consensus, related thresholds determine when validator attestations can justify or finalize blocks. Multisignature wallets use an approval threshold, such as three of five signers, for transactions.
Threshold design creates a tradeoff between legitimacy and liveness. If quorum is too low, coordinated insiders or a temporary borrower of voting tokens may control a decision. If it is too high, inactive holders can block every proposal without voting. Lost keys, exchange custody, delegated tokens, and supply that cannot practically participate can make a percentage that looks reasonable on paper impossible to reach.
Projects use several approaches to improve the balance. Dynamic quorum can adjust requirements using historical turnout or opposition. Delegation lets inactive holders assign voting power to active representatives. Separate proposal categories can require stronger participation for contract upgrades or treasury transfers than for routine grants. Timelocks and veto councils may add protection, but also introduce new trust and centralization concerns.
When evaluating quorum rules, check the eligible supply definition, snapshot block, delegation treatment, abstention rules, approval threshold, and cancellation powers. Review actual turnout and holder concentration rather than only the published percentage. Governance systems should explain how emergency decisions and repeated failures are handled. A well-designed quorum makes capture harder without allowing inactivity to freeze the protocol indefinitely.
Frequently asked questions
- Quorum can be a fixed number of participants, a percentage of eligible voting power, or a threshold based on votes cast for selected options. The right level depends on ownership concentration, normal turnout, delegation, and decision importance. Designers should use historical participation data, publish the calculation clearly, and avoid rules that one large holder can satisfy alone.
- The proposal normally fails, expires, or remains invalid even when most participating voters supported it. The exact result depends on governance rules. Proponents may revise and submit it again after improving communication or delegation. An unmet quorum should not be treated automatically as opposition because eligible voters may be inactive, unaware, technically blocked, or deliberately abstaining.
- Yes. An excessive threshold can prevent routine upgrades, budgets, or emergency responses even when active participants strongly agree. This gives inactive voters an effective veto and may encourage off-chain workarounds. A threshold that is too low creates the opposite risk by letting a small group act for everyone. Different proposal types may justify different quorum and approval requirements.