About the BIP | Badger Improvement Proposals category

Badger Improvement Proposal

A BIP is a proposal to signal or effect change to BadgerDAO’s governance or products. The objective for a BIP is to engage the community so that we can come together on a decision regarding a specific topic and put it into action. It must be a complete proposal that is clear, concise, and unambiguous.

Below, we’ve outlined the initial framework for governance. This will be a living document/framework as we continue to expand and adapt as necessary.

Table of Contents

  1. Governance Process
  2. BIP Template
  3. Accepting and rejecting BIPs
  4. Next Steps

1. Governance Process

  • Forum - All major discussions must start here in the form of a BIP. For any proposal to make it to a snapshot, it must reach a quorum of at least 40 votes.

  • Snapshot - Only select people (for now, operations team) will be allowed to push approved forums proposals to snapshot. As we continue to establish the infrastructure, this is subject to change.

  • Execution - If approved via snapshot then either the multisig or through DAO vote will execute the proposal that garners supermajority support.

2. BIP Template

BIPs must follow this template:

  1. Name, scope, and objective.
  2. Categorize the BIP into one of the following: Emissions, Sett Vault, Governance, New Product, or Other.
  3. Provide a high-level overview of the BIP.
  4. Provide low-level details of the BIP.
  5. Business and technical requirements of the implementation of the proposal.

3. Accepting and rejecting BIPs

  1. Once submitted, the BIP should be open for discussion for at least 5 days (assuming it is well-formed). The BIP can be left open for longer if the content is highly contested or no consensus for path forward is reached. During the early stages of expansion, we may move with greater agility.
  2. While the BIP is open, the team and community should present arguments to justify its acceptance or rejection.
  3. After one week, the Governance Facilitator or Ops Team will determine if consensus has been reached for the content of the BIP. If there are changes necessary, they will synthesize/modify in a comment which will then be pushed forward to snapshot.
  4. If the BIP has a majority support from the community, the team will signal that it has been accepted.

When a decision is made, it will be clearly signalled on the BIP thread. Regardless of acceptance or rejection, if the reasoning is not clear from the discussion in thread, the team will provide a rationale for the decision. All community members are encouraged to challenge any decisions that they think have been made in error.

4. Next Steps

After a BIP is accepted, the Badger core development team will add the implementation details to the development backlog. When relevant to the circumstances, it may include an indication of priority and estimated delivery date (where possible).

Acknowledgements

The BIP process is a modified version of https://github.com/rust-lang/rfcs 2. The template also draws inspiration from one of our Badger Builder partners: forum.renproject.io.

10 Likes

Hey team. I posted a BIP proposal and its gone to an admin for review. When/how does that process work?
Many thanks

1 Like

I did the same. I see in #governance on Discord DeFi Frog says:

Hoping to make this abundantly clear - BIPs that are submitted for review that do not follow the template will be rejected. Please follow the guidelines made in the forum.

I believe mine did follow the template as I copied the format of previous BIPs, but I will resubmit with a fine-tooth comb for detail.

1 Like

down the rabbit hole we go…

Hi there, I am new here and I hope to participate :slight_smile: xoxoxo just reading how to do it lol