Proposal Process

The process for getting a proposal enacted begins with a post in the Discussion category of the CGDAO forum. In order for a proposal to be voted on it must go through the proper phases of the proposal process based on its impact. Most ideas will spawn from conversations through other official CG portals such as the Discord or Telegram, but any significant input should be funneled to the the official forum.

(Phase 1) Discussion

Subcategories = Site Feedback

About: Discussion is the starting point for ideas and potential proposals to advance through community participation. Think of it as a “Temperature Check”.

• Following at least 3 days of discussions, the user can signal escalation to the next phase by commenting on the thread and linking to the new topic.

• Please refrain from escalating ideas that do not gain the appropriate attention and engagement as this will lead to wasted proposals and unfavorable outcomes.

• If low activity/interest has been recorded and/or core council members show no involvement in discussions; then the community admins have the right to close the submitted topic and not allow escalation to the Draft Review, Proposal or Governance phases.

(Phase 2) Draft Review

Subcategories = N/A

About: Draft Review is for formal discussion and review of structured draft proposals. This phase helps gain broader consensus before escalating to a formal proposal.

• In cases where a proposal has a low impact and does not affect core or governance protocols, users can skip this phase and go straight to a Proposal level review and vote. Learn more about Templates.

• Minimum of 3 days for draft review.

• Proposals can be edited and refined based on community feedback at this time.

• The user who submitted the proposal must signal an admin by direct message before a Snapshot vote can be created.

• After the draft review period, the user can submit a Snapshot poll.

• Proposals in this phase require a voting period of 4 days.

• For Basic Voting and Single choice voting a 51% approval is needed to pass the proposal.

• If the vote passes, then the user can escalate to the final phase.

• Any proposal that has a failing vote will be closed and locked.

• After a failed vote, a proposal can be rewritten and submitted only once more.

• All proposals in phase 2 should have a link to the original discussion and the current Snapshot vote.

• All high-impact proposals must go through this phase.

(Phase 3) Proposals

Subcategories = ChainBoost, Cryptoverse, ChainGuardians, Treasury

About: For submission and review of finalized proposals that are ready to be voted on. Proposals that reach this point have gone through periods of community discussion and review.

• Proposals should be presented in their most accurate, verbose, and complete form. Learn more on the Proposal Templates page.

• Minimum of a 3 day review period.

• Proposals can be edited and refined based on community feedback at this time.

• After the review period, the user can submit a Snapshot poll.

• Low impact proposals in this phase require a voting period of 4 days.

• High impact proposals in this phase require a voting period of 7 days.

• The user who submitted the proposal must signal an admin by direct message before a Snapshot vote can be created.

• All submitted proposals must have a link to the current Snapshot vote, and previous discussion threads.

• After voting ends, there will be a 2 day failsafe period. This is for catching potential vulnerabilities and any other security threat that might have been missed. If low impact this can be lowered.

• For Basic Voting and Single choice voting a 51% approval is needed to pass the proposal.

• If the vote passes, then the DAO Committee or GB will sign the necessary transaction, or complete any appropriate action needed in agreement with the proposal outcome and the will of the people.

• Any proposal that has a passing vote will be closed and implemented after the 2 day failsafe period.

• Any proposal that has a failing vote will be closed and moved to the “Archives” section.

• If a vote fails to pass in this phase, the user must wait 1 week before resubmission.

(Phase 3 GIP) Governance

Subcategories = Gov-meta, Constitution, Election

About: Governance is only for proposals focused on governance protocol or process changes. It is the final review process for any Guardian Improvement Proposal (GIP). Election proposals for council members will also take place here.

• Proposals should be presented in their most accurate, verbose, and complete form. Learn more on the Proposal Templates page.

• Minimum of 3 day review period.

• Proposals can be edited and refined based on community feedback at this time.

• After the review period, the user can submit a Snapshot poll.

• Proposals in this phase require a voting period of 7 days.

• The user who submitted the proposal must signal an admin by direct message before a Snapshot vote can be created.

• All submitted proposals must have a link to the current Snapshot vote, and previous discussion threads.

• After voting ends, there will be a 2 day failsafe period. This is for catching potential vulnerabilities and any other security threat that might have been missed.

• For Basic Voting and Single choice voting a 51% approval is needed to pass the proposal.

• If the vote passes then the DAO Committee or GB will sign the necessary transaction and complete any appropriate action needed in agreement with the proposal's outcome and the will of the people, upon which the CG team will begin execution.

• Any proposal that has a passing vote will be closed and implemented after the 2 day failsafe period.

• Any proposal that has a failing vote will be closed and moved to the “Archives” section.

• If a vote fails to pass in this phase then the user must wait 1 week before resubmission.

Important: Any significant edits to Draft Review and Proposal posts require a 24-hour review period.