Formal Proposals
The Increment community uses:
Discourse for discussing protocol improvements and formulating proposals to be voted on,
Snapshot for voting and signalling sentiment offchain, and
Aragon where votes are delegated and cast through for onchain execution
The protocol heavily relies on the voice of our community and that is where you can put your thoughts into action.
Visit the Governance section in Developer Docs to see the complete list of parameters that governance can change.
Increment implements a straightforward and iterative 3 stage governance structure:
Proposal Discussion
Anyone can post and discuss new ideas informally on the Increment community forum to build momentum inside the community.
Duration: No minimum or maximum time frame on how long a proposal remains in this phase
Who: Anyone can post
Requirements: No formal requirements
Stage 1: Increment Ecosystem Proposal (IEP) - Temperature Check
An IEP provides a structured overview of the proposal that acts as the basis for further discussions and also as foundation for decision making during the next phase. This temperature check is used to garner the community's interest and build consensus
Duration: No minimum or maximum time frame on how long a proposal remains in this phase
Who: Anyone can create an IEP.
Requirements: Post in the IEP section of the Increment community forum.
Template: The template is available on Discourse and can be found here.
Stage 2: Increment Ecosystem Proposal (IEP) - Consensus Check
After the IEP has been posted in the community forum, the formal proposal needs a Snapshot vote to measure consensus. This is last step before conducting an onchain vote.
Duration: 3 days
Who: Hold or be delegated at least 100 gINCR is required to create a proposal
Quorum requirement: 2% of gINCR supply has to participate
Template: The template is available on Discourse and can be found here. Make any changes necessary and also include a link to the IEP discussion from Stage 1.
Outcome: If the Consensus Check does not suggest a change, the topic will be closed on the governance site. If the Consensus Check does suggest a change, proceed to the next stage.
Stage 3: Increment Ecosystem Proposal (IEP) - Onchain Vote
The final execution of an IEP requires a successful onchain vote by the community. This will be done on Aragon. Duration: 7 days
Who: Hold or be delegated at least 100 INCR is required to create a proposal
Quorum requirement: 2% of gINCR supply
Procedure:
Write the code for your proposal, which will be voted on through Aragon. All proposed code should be audited by a professional auditor.
Ensure that you have at least 100 INCR delegated to your address in order to submit a proposal, or find someone who has enough INCR to meet the proposal threshold to propose on your behalf.
Following the following guide to make a successful proposal. Make sure to link all previous Consensus and Temperature checks from Discourse and Snapshot.
Outcome: If quorum is reached, then the winning outcome will be executed. If quorum is not reached, the proposal will be rejected. If the winning outcome is “Make no changes” or “Against”, the proposal will be rejected.
What really matters is Stage 3 onchain execution through the Aragon interface, but the initial Stages 0 - 2 used for discussion and sentiment signalling are still important to build momentum in the community.
You can skip them if you are confident enough, but if you skip them, it is possible that no one understands or anticipates your proposal so it will decrease the likelihood of your proposal being voted through.
Last updated