Community Governance Process

The Community Governance Process is distributed across many steps and it takes place in different online platforms.

There are 3 main portals that are used by the Idle community to drive an idea from early stage to execution:

Idle Forum
It is a Discourse forum that collects the discussions related to Governance and protocol improvements.

Idle Snapshot Page
This interface allows community members to signal their voting sentiment regarding a possible proposal. This is an off-chain action and it does not influence the Voting Phase of an IIP.

Governance Dashboard
The Idle dashboard is the interface that allows community members to cast votes on-chain and determine if an IIP will be approved or not. It also allows delegation of voting rights to third parties. Other platforms might integrate Idle protocol and provide voting features.

Now that we have described the portals, we list the processes. These steps may change in the future, according to the community’s will.

IIPs are formal on-chain proposals that are executed if the majority (50% +1) of the voters cast a “For” vote and at least 4% of the total voting right supply [520,000 IDLE] has casted a vote on that proposal, in favor or against.

Community members can create a proposal if they have at least 130,000 IDLE as delegated votes and hold them during the entire voting process (up to the implementation).

Idle’s architecture has been inspired by the COMP Governance modules, that govern the Compound protocol, and the Uniswap Governance Process.

The proposal journey consists of 7 steps:

  1. Ideation & Discussion Phase: community members can propose early stage ideas in the Idle Forum (“Governance-Meta” or “New Features & Improvements” category) and receive initial feedback.
    Governance-Meta” includes discussion about how the Governance works and how we can improve it; “New Features & Improvements” embraces topics like the creation of new products, ecosystem grants, integrators programs, and tech changes of the current protocol.
  2. Temperature Check: write a post on the Idle Forum (Temperature Check category) with the title: “[Temperature Check] - Your Title Here” and create the associated Snapshot poll on the Idle Snapshot Page. The voting process is a secure off-chain action and requires that voters only sign a message; the Snapshot poll takes into account the IDLE held in an address and not the delegated voting power.
    The aim is to taste the sentiment of the community about a potential change.
    The Snapshot poll should last for 3 days and voters indicate their interest in bringing it forward to the next stage. You need to hold 100 IDLE as voting power to submit a Snapshot poll.
  3. Forum Proposal: once the idea is more structured and has the form of a proposal, the initial proposer or a community member may decide to submit the idea as an IIP in the “Proposals” category on the Forum. Check “How To Propose an IIP”. Write a post labeled as follows: “[Proposal] - Your Title Here”. Here it can be further discussed among IDLE token holders and fine tuned.
    It is recommended to perform third-party audits before advancing to the next step. This means that a further IIP about code audit, financed through the ecosystem fund, should be launched and approved before the code implementation proposal.
  4. Consensus Check: Write a new post in the Consensus Check category titled “[Consensus Check] — Your Title Here” and create the associated Snapshot poll on the Idle Snapshot Page. This means that the IIP already passed the Forum discussion and is almost ready for the on-chain journey.
    The voting process is a secure off-chain action and requires that voters only sign a message. The Snapshot poll takes into account the IDLE held in an address and not the delegated voting power.
    The Snapshot poll should last for 3 days and if the “For” vote wins, the proposal can land on-chain. You need to hold 100 IDLE as voting power to submit a Snapshot poll.
  5. Pending State: the proposer or other people can deploy on-chain the official proposal, that is broadcasted as executable code. It starts its journey in a pending state.
  6. Voting Phase: once the on-chain proposal is active, IDLE token holders cast their vote “For” or “Against”. The voting phase lasts 3 days since the activation of the proposal.
  7. Execution Phase: if the quorum is met, the proposal can be executed 2 days after the closing of the voting phase (and no later than 14 days), remaining queued during that grace period.
    If rejected, then the IIP will move to the ‘Rejected’ stage and the associated code will not be executed.

Please read the Forum Guidelines.

Some useful links:
Website
Discord
Official Documentation
Github

1 Like

In the last month the community worked on the Smart Treasury, iterating and brainstorming on the next steps and proposal specifications. Smart Treasury proposal has been widely discussed and approved by the Governance, with at least 90% of the voters always in favour of the initiative.

We noticed some legitimate doubts in the community regarding the need of the Consensus Check to confirm a clear Governance will. These guidelines have been initially inspired by the Uniswap Governance Process, where the Consensus Check should last 5 days. Taking the Smart Treasury as a reference, we propose to let some proposals skip that additional poll if previously and extensively discussed in the forum.

This update reduces the Consensus check duration from 5 to 3 days, and makes it “strongly suggested” only for ideas that are posted as IIP with public discussions. IIPs that will come without any previous community discussion would require a Consensus Check.

Drop a comment below if you have any suggestion to further improve the process!

3 Likes