Once the community has decided a proposal discussion is ready to be voted on, they should make a proposal in the Proposal Discussion section of the forum.
Any formal proposal must:
receive at least ( 5 ) thumbs up
be live for ( 5 ) days
follow this template.
Otherwise, it will not be considered a valid proposal and removed.
Once that’s been done, formal voting can take place.
Off-chain voting or "soft voting" - This kind of voting will take place on Snapshot, a simple voting interface that allows users to sign (no transaction fees). Votes on snapshot are weighted by the number of HACHI delegated to the address used to vote.
IMPORTANT: For now, Snapshot will be used for final decision making - you can access the Akita DAO Snapshot here.
Conflicting Votes
From time to time there may be conflicting proposals, to avoid issues, the 5 day window above can also serve as time for anyone to list their preferred alternative option on the forum. Each proposal on an associate topic will have a [TOPIC] block placed in its title.
After that time, a vote will be put forward including all options available to move forward with. This will ensure that everyone has the ability to express their preferences while keeping decision timelines reasonably short.
Remember, this is a living document and is only meant to act as a starting point for governance. If there’s anything you want to add or anything that’s unclear please suggest it below or even as a separate proposal!
Community Proposal
An AKITA Community Proposal is a format for making decisions about how our community grows. Key points to keep in mind include:
Title - Post each proposal with a clear title around its objective. This will look as follows: [Proposal] - XXXXXX
Ordering - Please do not assign a number to your proposals. The ordering of the proposal will be assigned by community moderators.
Detail - While we encourage everyone to participate, please try to consider all viewpoints and provide a deep level or detail regarding the thoughts that went into a proposal.
Voting - Not every proposal will be voted on. There is no hard criteria regarding what deems a proposal eligible to be implemented, though a good rule of thumb is the more engagement it has, the more likely it is to be incorporated.
Ethos - The goal of governance is to create a more inclusive and empowering system for all stakeholders. We encourage proposal creators to center their ideas around how a proposal helps AKITA users, partners and team members better interact with one another, and how these changes create a more fluent ecosystem for all those interacting with the protocol.
When you’re ready to submit a proposal, please follow this format to the best of your ability. Proposal Format:
Summary - 2-3 sentences on what the proposal is and what changes are being suggested without going into deep detail.
Abstract - Expanded summary introducing the proposal, what it entails and details around what would change should the proposal be implemented.
Motivation - Describe the motivation behind the proposal, the problem(s) it solves and the value it adds. This is your chance to show why this proposal is necessary, and how the changes would benefit AKITA if implemented.
Specification - Describe the “meat & potatoes” of the proposal. Go into deep detail around the changes that will happen both on a technical and social level. The more detail, the better.
Benefits - Point out core benefits of the proposal implementation and how it will affect the system.
Drawbacks - Highlight any drawbacks from implementing the proposal and points to consider regarding the upgrade.
Vote - Clearly outline what voting “yes” and “no” entails. Please link to Snapshot 35 or include a forum poll directly on the forum to get a temperature check under Setting > Build Poll to vote.
When mapping out a vote, remember the following:
For - Formalizes the community is “for” the details outlined in this proposal including xyz…
Against - Formalizes the community is “against” the proposal including xyz…
