Comment on page
Community Governance Process
This page outlines the process for governance proposals that originate in the community.
If you are interested in submitting a proposal to the Alchemix DAO, then you will need to follow the process below.
It is recommended you gather sentiment for your proposal idea through discussion with the community in the discord server, fireside chats, DMs with other community members, and/or writing a draft document to share.
Share the Alchemix forum link to your proposal in the #governance-proposals channel in the Alchemix discord server at discord.com/invite/alchemix.
After a minimum of 5 days have passed since completing Step 1 AND Step 2, you may post your proposal to the “Alchemixed Opinions” Snapshot (the platform for Alchemix governance temperature checks). Snapshot link: https://snapshot.org/#/alchemixedopinions.eth
- 1.A minimum of 50 ALCX is necessary to post a proposal. If you do not have 50 ALCX, you can ask someone with 50 ALCX to post on your behalf.
- 2.Proposals will be live for 3 days.
- 3.Voting options must only be For, Against, or Abstain.
If greater than 50% of the non-abstain vote is “For”, and a quorum of 5k ALCX voting is met, the proposal will move to the official Alchemix Proposal Snapshot as an AIP (Alchemix Improvement Proposal) at https://snapshot.org/#/alchemixstakers.eth
Official AIPs will have a quorum of 35k ALCX. If quorum is met, then the multisig will be directed to execute the most popular voting option unless directed otherwise by the voting parameters.
- 1.A change to the protocol treasury and/or how it is utilized.
- 2.A change to protocol parameters (such as transmuter flow rate).
- 3.A grant, donation, or funding request.
- 4.Deploying a new protocol-related contract or contract upgrade (ie, deploying a new yield strategy or deploying on a new chain).
- 1.The first item in the proposal should summarize only the action items on what exactly is being proposed. It should not include any justification in order to be as succinct as possible.
- 2.The introduction of the proposal should be an introduction giving context to the reason for the proposal and what the body of the proposal contains.
- 3.The body of the proposal should include in-depth analysis and justification for what is being proposed.
- 4.The end of the proposal should state the voting options that will appear on snapshot and what they mean (For, Against, Abstain).
- 5.Any proposal that requires a high level of effort (new features, new deployments, grant requests etc) should identify who is going to do the work. For example, a poorly written proposal would simply suggest a new feature. A well written proposal would suggest a new feature and provide verification that Core team is willing and able to build the feature, OR it should state who is building the feature. If a grant request is included, then there is more onus on the proposer to justify why they will be able to build the feature. Treasury actions and changing protocol parameters will typically only take a handful of multisig transactions - in these cases it can be assumed the multisig will carry out the proposal if passed.