Best Practices : Akash Governance Proposal's

[CaptainSplince]

Overview

This document gives best practices for how to best prepare for requesting resources from the community pool at present and the Incentive Distribution Pools after the full implementation of AKT2.0 in the future. Here are some guidelines to help structure your ideas before they become proposals.

Prepare the prerequisites

• Join Akash’s Discord.
  • By joining our discord, you’ll have access to a wealth of resources and the opportunity to engage our community with questions and discuss your early-stage ideas. This is a good place to gut-check your ideas.
• Do your research and answer these key questions:
  • What is the problem you’re trying to solve?
  • Play devil’s advocate: are there reasons your idea might not work?
  • Is work already being done somewhere in the Akash Community?
• Is the project you’re working on open-source or closed?
  • Open Source: Projects should be built in the spirit of open-sourcing your learnings for everyone to learn from.
  • Public Good: There should be a clear connection between your proposal and the value it generates for the broader community.
  • Clear Use of Funds: Present a clear plan for how the funding will help your goals.
• Review current working groups, GH discussions, and/or SiGs (on GH and Discord) to talk about your ideas with others in the community. Don’t be shy!
• Create projected outcomes that are specific, measurable, and time-bound
  Projected timelines for deliverables that are broken into quarters are best. If a project could take a year to complete, break it down into discrete quarterly milestones that can be measured and tracked.
• Note: If you are awarded public funds, it’s important to show accountability to the community. Construct how and what potential AKT liquidations would look like for funding your project. Reporting and accountability on the use of public funds should be made open and shared with the community

Create an initial draft of the proposal

• Post it on GH discussions with the above prerequisites satisfied to the best of your ability. The Overclock Labs core team and Akash Community can always provide feedback and help.
• If it is a technical solution (feature request, enhancement, etc), detail out the deliverables, what it entails, and create a document known as a PRD (if needed), along with estimated hours, hourly rate for a total value to show how you arrived at the funding request. These should be a collection of interactions you’ve discussed with the community, or core teams in the SIG/WG’s you’ve attended leading up to this point. The Steering Committee and SIGs/WG’s are resources, use them for guidance.

Use Akash Discord, GH “Discussions”, and/or WG/SIG meetings for detailed conversations that should feedback into the draft proposal

• Join Special Interest Group (SIG) or Work Group (WG) channel
• Join one of the SIGs or WG channels and introduce yourself and your idea, gathering feedback to iterate and refine.
  Full list of SIGs and WGs (under “Core Community Groups”)
• Join SIG or WG monthly call
  • This is an opportunity to get feedback for your idea directly from the community
  • Events happen monthly.

Finalize Proposal

Once the discussions in the channels previously mentioned have run their course, then:

• Draft your “final” proposal and share when you plan to put your proposal onchain

How to submit a proposal

• Create the proposal yourself. If you don’t know how to do this, reach out on Discord for help.
  • TBD: which group in discord
• Find and reach out to an Akash Validator that can put your proposal on-chain for a vote
• Share your proposal in the Validators channel in the Akash Discord. Ask the validator community for feedback. Connect with validators that have shown interest in supporting your proposal.
• NOTE: all proposals require a 1000 AKT deposit to go on-chain for a vote
  • Voting inner workings
  • How to reach quorum

Once the Proposal is on chain

• Let the community know on Discord, Telegram, and Twitter. Overclock’s team, and Akash Network Insiders and Vanguard’s are proactive in supporting proposals designed to benefit the community and network growth.

Proposal Framework:

Prerequisites

• Proposal Research

  • Describe in detail, how you researched your proposal idea.
  • What available data do you have for your proposal?
  • Who did you consult with to help define your proposal goals?
  • If it is a technical-related solution (feature request, enhancement, etc), detail out the deliverables, what it entails, and link the PRD (if needed), along with estimated hours, hourly rate for a total value to show how you arrived at the funding request. These should be a collection of interactions you’ve discussed with the community, or core teams in the SIG/WG’s you’ve attended leading up to this point. The Steering Committee and SIGs/WG’s are resources, use them for guidance.

• Proposal Projected Outcomes

  • Forecast the outcomes of your proposal.
  • Give detailed information on how it will impact the growth of the network. How will we measure success?

• Proposal Timeline

  • Describe the steps required to complete your proposal tasks.
  • Rule of thumb; keep funding limited to quarterly-based initiatives unless feedback from the Steering Committee directs otherwise.

• Draft an overview of your proposal.

  • Describe how you came up with the idea, the problem you’re aiming to solve, and how your proposal will offer a solution
  • Props should be shared in GH discussions to formalize
  • Once the prop discussions have run their course, this can lead to an official document (like a PRD)

• Proposal funding

  • Describe the resources you will need to accomplish your proposal. The more detailed you are in what you will use resources for, the better!

• Detail impact

  • If additional resources will be needed after initial resource allocation, including information on how those resources will be requested

• Previous Proposal Links

  • Passed
  • Not Passed