Popcorn Governance Process
PopcornDAO is aiding the revolutionary fusion of positive global impact and DeFi. The following governance processes will evolve as the DAO pursues its journey of DeFi for Good.
DAO governance lies at the heart of our mission to drive effective and sustainable impact around the globe. Clear governance guidelines help our community make decisions efficiently and make sure that as many voices are heard as possible.
Please read, abide by, and help refine the following guidelines so that we can grow Popcorn in the most impactful way possible.
TL;DR: Post a Request for Comment (RFC) using the template at the bottom of this post. Wait at least 3 days for responses. Respond to comments, summarize the RFC, then post it to the Popcorn Improvement Proposal (PIP) category. Wait at least 3 more days for a forum vote on your PIP. It can then move onto a Snapshot vote.
The following framework was initially modeled after the Abracadabra Governance Process .
Table of Contents
II. Governance Process
- Post a Request for Comment (RFC)
- Summarize the RFC
- Submit a Popcorn Improvement Proposal (PIP)
- Participate in Snapshot Vote
- Process Results
III. RFC/PIP Templates
Proposal creation, voting, and processing is carried out by PopcornDAO governance. The purpose of proposals is to build upon or change features of Popcorn, such as adding beneficiaries, requesting protocol changes, or allocating treasury funds.
Proposals can arise from discussions held in Discord or the forum, or can be based on an individual DAO member’s own expertise. Once the idea has been developed, the first step in the proposal submission process is: 1. Post a Request for Comment (RFC). This invites other PopcornDAO members to provide their feedback.
After a robust discussion, the next step is: 2. Summarize the updated RFC. Proposal changes should be noted and timestamped in a changelog at the bottom of the post.
The matured idea can then be submitted as a 3. Popcorn Improvement Proposal (PIP). PIPs that are determined by a mod/core contributor to be clear, adequately debated, and in line with the overall Popcorn mission will go to a forum vote. PIPs that pass the forum voting process (with a minimum of 20 total votes) will then go to a Snapshot vote.
Proposals that are well-defined and unambiguous from the start can be submitted directly as PIPs, bypassing the RFC. However, mods are more likely to approve a PIP if it has been preceded by a robust discussion. Therefore it is recommended to follow the path of RFC → PIP if you have a proposal idea.
II. Governance Process
1. Post a Request for Comment (RFC)
Most proposal ideas arise out of community chats, so consider bouncing your idea around in Discord or in the forum before posting an RFC.
The purpose of a Request for Comment is to grow your idea via community feedback. To begin this first step, fill out the RFC template and post in the relevant forum. Give the community some time to understand your idea and be sure to respond to commenters. Be open to suggestions that could improve your idea and help it come to fruition. Proposals are a collaborative process from the start!
Try your best to address any challenges that arise while you gauge the overall community sentiment on your proposal. Once your idea has been refined through DAO member commentary, you can update and summarize it.
2. Summarize the RFC
Summarizing any updates to your proposal, as well as relevant discussions, will help DAO members understand the full scope of your idea. If appropriate, summarize the arguments you heard both for and against your proposal. Proposal changes should be noted and timestamped in a changelog at the bottom of the post.
At this stage, you can gauge whether your RFC is ready to be submitted as a Popcorn Improvement Proposal (PIP). RFC summaries can go through many iterations based on additional discussions that take place on the forum.
3. Submit a Popcorn Improvement Proposal (PIP)
If your matured RFC is ready to move on to the next step, post your proposal into the PIP forum category. Include a link to your RFC thread in your PIP post and a tl;dr summary. In rare cases, proposals can be submitted directly as PIPs, foregoing the RFC process, but this exception should be reserved only for thoroughly developed or highly time-sensitive proposals.
PIPs that are determined by a mod/core contributor to meet PIP standards will then go to a forum vote. Forum votes are used as a way to gauge overall community sentiment and determine whether there is ample support for it to pass a Snapshot vote. Share your PIP in Discord and give the community at least three days to process and vote on it.
4. Participate in Snapshot Vote
If your PIP passes its forum vote with a minimum of 20 votes, it can proceed as a Snapshot vote. Provide a core team member with the content of your PIP along with the relevant forum discussion links. Snapshot votes are the final step for POP holders to ratify the proposal into DAO governance.
5. Process Results
If the PIP is approved in the Snapshot vote, DAO contributors will be tasked with implementing the proposal in a timely manner. Your proposal has popped from an idea-kernel into PopcornDAO governance!
III. RFC/PIP Template
The following template should be used as a basis for your proposal. It’s not necessary for every section of the template to be filled out for the first iteration of an RFC.
1. Summary/Scope: This is where you provide a tl;dr overview of your proposal. Busy DAO members will thank you for this!
2. Link to previous DAO discussions: Here, you’ll link to any forum posts or Discord threads that have informed your proposal.
3. Main Objective: This is where you deeply explore the what, why, when, and how of your proposal. What does your proposal do to further the mission of Popcorn? Try to indicate any potential risks or drawbacks to your idea, along with its potential benefits. This is also the place to summarize community feedback as it arises.
4. Contracts/Technical Requirements: What kind of work would need to be done by developer teams to carry out your proposal?
5. Organizational/Partnership Requirements: What kind of work would need to be done by non-developer teams to carry out your proposal?
6. Next Steps: What are the next steps to be carried out by DAO contributors if your proposal is approved?
7. References: Here, you’ll provide any references you used to develop your proposal along with any other relevant content to be considered.