Audius Improvement Proposals (AIPs) Explainer

This post will walk through how to make a formal governance proposal.

An Audius Improvement Proposal (AIP) is a mechanism for suggesting protocol upgrades through the governance forum and on-chain governance dashboard. Key points to keep in mind include:

  • Title - Post each proposal with a clear title around its objective. This will look as follows: [Proposal] - $AUDIO Grant
  • Ordering - Please do not assign a number to your AIP. The ordering of the proposal will be assigned by community moderators when it’s ready to be moved to an on-chain vote.
  • 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 make its way to an on-chain vote. There is no hard criteria regarding what deems a proposal eligible for a vote, though a good rule of thumb is the more engagement a proposal has, the more likely it is to be put to a vote.
  • 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 Audius 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. Should a proposal receive enough community support, it could be moved to the Governance Dashboard for AUDIO-weighted voting.

AIP Format:

  1. Summary - 2-3 sentences on what the proposal is and what changes are being suggested without going into deep detail.
  2. Abstract - Expanded summary introducing the proposal, what it entails and details around what would change should the proposal be implemented.
  3. Motivation - Describe the motivation behind the proposal, the problem(s) it solves and the value it adds. This is your chance to show how you reached the conclusions that this proposal is necessary, and how the changes would benefit the protocol if implemented.
  4. 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.
  5. Benefits - Point out core benefits of the proposal implementation and how it will affect the system.
  6. Drawbacks - Highlight any drawbacks from implementing the proposal and points to consider regarding the upgrade.
  7. Vote - Clearly outline what voting “yes” and “no” entails. Please link to Discord or a forum poll to vote.

For: Formalizes the community is “for” the details outlined in this proposal including xyz…
Against: Formalizes the community is “against” the proposal including xyz…

More details regarding the on-chain aspects of an Audius proposal to be shared here shortly.

For questions, comments or concerns on any of the above, please message @coopahtroopa on Twitter, Discord - @coopahtroopa#9799 or Telegram - @coopahtroopnew