A proposal threshold is the minimum amount of governance power—typically measured in tokens—a user must hold or delegate to formally submit a governance proposal for a community vote. This mechanism acts as a spam filter and quality control measure, preventing the governance system from being flooded with frivolous or malicious submissions. It ensures that proposal submitters have a meaningful skin in the game, aligning their incentives with the protocol's long-term health. The threshold is usually defined in the protocol's smart contracts and can be adjusted through a governance vote itself.
Proposal Threshold
What is Proposal Threshold?
A quantitative gatekeeping rule in decentralized governance systems that determines who can submit a formal proposal.
The specific implementation of a proposal threshold varies by protocol. In systems like Compound and Uniswap, it is expressed as a fixed number of governance tokens (e.g., 65,000 COMP or 10,000,000 UNI). Other DAOs may use a dynamic threshold based on a percentage of the total token supply or delegated voting power. This design choice balances accessibility with efficiency; a threshold set too high can centralize proposal power, while one set too low can lead to governance paralysis due to proposal overload.
To meet a proposal threshold, users who do not hold enough tokens individually can participate in delegate strategies, such as forming a governance pod or rallying support from a decentralized autonomous organization (DAO) sub-group. Alternatively, they can use platforms that aggregate voting power from multiple stakeholders to sponsor proposals. The threshold is distinct from a quorum, which is the minimum voter participation required for a proposal to be valid, and from a passing threshold, which is the majority vote needed for execution.
Adjusting the proposal threshold is a critical governance decision. As a protocol matures and its token distribution changes, the community may vote to increase the threshold to maintain proposal quality or decrease it to encourage broader participation. Historical examples include MakerDAO's iterative adjustments to its governance parameters to optimize for stability and inclusivity. These changes are often debated in governance forums long before a formal vote, highlighting the threshold's role in shaping the political and operational dynamics of a decentralized community.
How a Proposal Threshold Works
A proposal threshold is a fundamental governance parameter that determines who can submit formal proposals to a decentralized autonomous organization (DAO) or blockchain protocol.
A proposal threshold is the minimum amount of governance power—typically measured in a protocol's native token—that a user must possess and stake or delegate to create an on-chain governance proposal. This mechanism acts as a spam filter, preventing the proposal queue from being flooded with frivolous or malicious submissions that would waste community attention and network resources. The threshold is usually defined as a specific token quantity (e.g., 100,000 UNI) or a percentage of the total voting supply, and is enforced automatically by the protocol's smart contracts.
Setting the threshold involves a critical trade-off between accessibility and efficiency. A threshold set too low may lead to governance proposal spam, overwhelming voters and making serious debate difficult. Conversely, a threshold set too high can centralize proposal power among a small group of large token holders or whales, stifling broader community participation. Many protocols initially set a high threshold for security and later adjust it via governance votes as the ecosystem matures and token distribution widens.
The threshold is often distinct from a quorum, which is the minimum voter turnout required for a proposal to pass. A user must meet the proposal threshold to submit a proposal, but the entire community must meet the quorum to validate its outcome. In systems like Compound and Uniswap, this threshold is a publicly visible, immutable parameter in the governance contract, though it can be changed through a successful governance vote itself.
In practice, users who do not individually hold enough tokens can collaborate to meet a proposal threshold through delegation or by forming a governance pod. Delegation allows smaller holders to pool their voting power with a trusted delegate who can then submit proposals. Alternatively, specialized platforms enable the creation of sub-DAOs or pods that aggregate tokens solely for the purpose of proposal submission, democratizing access while maintaining the spam-protection benefits of the threshold.
For developers and analysts, monitoring the proposal threshold is key to understanding a protocol's governance health. A threshold that consistently requires more than 1-2% of the circulating supply may indicate excessive centralization. Historical analysis of successful proposals can reveal whether the threshold is effectively filtering noise without excluding meaningful community initiatives, providing critical data for future parameter optimization.
Key Features of a Proposal Threshold
A proposal threshold is a governance parameter that defines the minimum amount of voting power (e.g., tokens) a user must hold to submit a formal on-chain proposal for community consideration.
Spam Prevention
The primary function is to prevent governance spam by requiring a significant stake to create a proposal. This filters out low-effort or malicious proposals, ensuring the community's attention is focused on substantive changes. It protects the governance process from being overwhelmed.
Stake-Based Access
The threshold is typically denominated in the protocol's governance token (e.g., 100,000 UNI, 65,000 MKR). This ties proposal creation rights directly to a user's skin in the game, aligning incentives with the protocol's long-term health. It is a form of proof-of-stake for governance participation.
Dynamic Adjustment
The threshold is not always static; it can be changed via a governance vote itself. This allows the community to calibrate governance accessibility in response to token distribution changes or participation levels. For example, a DAO might lower the threshold to encourage more proposals if participation is low.
Relationship to Quorum
It is distinct from quorum, which is the minimum total voting power required for a proposal to be valid after submission. The proposal threshold controls who can propose, while quorum determines if a proposal has enough participation to pass. Both are critical for legitimate outcomes.
Delegation Impact
Users can delegate their voting power to others, which can help delegates meet the proposal threshold. This concentrates proposal power in the hands of active, knowledgeable delegates, creating a representative or liquid democracy model where not every token holder needs to be an expert proposer.
Common Implementation Examples
- Compound: Requires 65,000 COMP (0.65% of supply) to propose.
- Uniswap: Historically required 10 million UNI (1% of supply), later reduced to 2.5 million.
- MakerDAO: Uses a Governance Security Module where proposals require an MKR deposit that is locked and subject to a delay before execution.
Examples of Proposal Thresholds
A proposal threshold is the minimum amount of governance tokens a user must hold to submit a new on-chain governance proposal. These examples illustrate how different protocols calibrate this critical parameter.
Proposal Threshold vs. Related Governance Parameters
A comparison of the proposal threshold with other core parameters that define how governance proposals are created, debated, and executed.
| Parameter | Proposal Threshold | Voting Delay | Voting Period | Execution Threshold / Quorum |
|---|---|---|---|---|
Primary Function | Minimum stake/tokens required to submit a proposal | Time between proposal submission and start of voting | Duration of the active voting phase | Minimum participation/vote weight required for a proposal to pass |
Typical Unit | Token quantity or percentage of total supply | Blocks or days | Blocks or days | Percentage of total supply or votes cast |
Governance Stage | Submission | Deliberation | Decision | Validation / Execution |
Common Value Range | 0.1% to 5% of token supply | 1 to 7 days | 3 to 14 days | 1% to 20% of supply (quorum) |
Primary Impact | Controls who can create proposals (barrier to spam) | Allows time for community review and debate | Determines the window for voters to cast votes | Ensures sufficient community support for legitimacy |
Effect if Too High | Centralizes proposal power, stifles innovation | Unnecessary delay in urgent matters | Reduces voter participation due to short window | Makes passing proposals nearly impossible |
Effect if Too Low | Spam proposals, governance attack surface | Insufficient time for due diligence | Voters may miss the voting window | Proposals pass with minimal support, risking instability |
Example (Compound) | 25,000 COMP | ~2 days (13,140 blocks) | ~3 days (19,710 blocks) | 400,000 COMP (quorum) |
Rationale and Purpose
This section explains the core logic and objectives behind implementing a proposal threshold in on-chain governance systems.
A proposal threshold is a governance parameter that establishes a minimum requirement—typically a quantity of voting tokens—that a user must meet to submit a formal governance proposal. Its primary purpose is to prevent governance spam and maintain the operational efficiency of the decision-making process. By requiring a meaningful stake, it filters out frivolous or malicious proposals that could otherwise overwhelm the community and dilute attention from substantive issues.
The rationale extends beyond simple spam prevention. A well-calibrated threshold ensures that proposal submitters have skin in the game, aligning their incentives with the long-term health of the protocol. This reduces the risk of proposals designed for short-term exploitation or that would be detrimental to the collective. Furthermore, it encourages coalition-building, as smaller stakeholders must collaborate to pool their tokens and reach the submission requirement, fostering broader community discussion before a proposal even reaches a vote.
Setting the threshold value is a critical governance decision itself. A threshold set too high can lead to governance capture by large token holders (whales) or entities, stifling participation and innovation from the broader community. Conversely, a threshold set too low fails its anti-spam function and can make governance practically unusable. Many protocols use a percentage of the total token supply (e.g., 0.25% to 1%) or a dynamic formula based on past participation to find this balance.
In practice, the proposal threshold works in concert with other governance parameters like quorum and voting delay. While the threshold controls entry into the proposal queue, quorum ensures sufficient participation for a valid vote, and a voting delay provides time for review. This creates a multi-layered system for quality control. For example, in Compound Governance, Proposal 62 famously established a threshold of 65,000 COMP, which was later adjusted by the community based on evolving needs and token distribution.
Security and Governance Considerations
The proposal threshold is a critical governance parameter that determines who can initiate formal votes, directly impacting a protocol's security and decentralization.
Definition & Purpose
A proposal threshold is the minimum amount of governance tokens a user must hold or delegate to submit a formal governance proposal for a community vote. Its primary purpose is to prevent governance spam and ensure proposals have a minimum level of stakeholder support before consuming community attention and on-chain resources.
Security Implications
Setting the threshold is a key security parameter.
- Too Low: Opens the system to spam attacks, where malicious actors flood governance with frivolous proposals, causing voter fatigue and obscuring critical votes.
- Too High: Can lead to governance capture by large token holders (whales) or centralized entities, stifling community participation and creating a plutocracy.
- Dynamic Adjustments: Some protocols implement thresholds that adjust based on total token supply or participation to maintain balance.
Common Implementation Models
Thresholds are implemented in several ways:
- Fixed Token Amount: A static number of tokens (e.g., 100,000 UNI). Simple but can become outdated.
- Percentage of Supply: A dynamic minimum based on circulating supply (e.g., 0.25% of total). Adjusts automatically with tokenomics.
- Delegated Voting Power: Counts tokens delegated to the proposer, allowing representatives of smaller holders to meet the threshold.
- Temporal/Reputation-Based: Used in forums like Compound's Governance v2, where past successful proposals lower future thresholds.
Interaction with Quorum & Voting Period
The proposal threshold works in concert with other governance parameters:
- Quorum: The minimum total votes required for a proposal to be valid. A high threshold with a low quorum can still allow small groups to pass proposals.
- Voting Delay/Period: The time between proposal submission and the vote, and the voting duration. These give the community time to review proposals that have passed the initial threshold.
- Timelock: A delay between a proposal passing and execution, providing a final security checkpoint.
Real-World Examples
- Uniswap: Fixed threshold of 10 million UNI (0.1% of initial supply).
- Compound: Uses a dynamic proposal threshold equal to 1% of the total COMP supply.
- Aave: Requires a minimum of 80,000 AAVE (delegated balances count) to submit a proposal.
- MakerDAO: Employs a complex Governance Security Module where proposals require a "signal" phase on forums before a formal on-chain vote, acting as a social threshold.
Strategic Considerations for DAOs
DAO founders and token holders must strategically set and adjust the threshold.
- Bootstrapping Phase: May start with a lower, founder-controlled threshold to ensure initial governance functionality.
- Path to Decentralization: Should have a clear, community-approved plan to increase the threshold or switch to a percentage model as adoption grows.
- Amendment Process: Changing the threshold itself is typically a governance decision, requiring a meta-governance proposal.
- Monitoring Tools: Use governance analytics platforms to track proposal submission rates and voter turnout to inform threshold adjustments.
Frequently Asked Questions (FAQ)
Common questions about the minimum voting power required to submit a governance proposal in a decentralized autonomous organization (DAO).
A proposal threshold is the minimum amount of governance tokens a user must hold or delegate to submit a formal proposal for a vote in a Decentralized Autonomous Organization (DAO). This mechanism acts as a spam filter, preventing the governance system from being flooded with frivolous or malicious proposals by requiring proposers to have a meaningful skin in the game. The specific threshold is typically defined as a percentage of the total token supply or a fixed token quantity and is set by the DAO's governance parameters. For example, a DAO with a 1% proposal threshold would require a member to control at least 1% of the total voting power to create a proposal.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.