Proposal for a formal BAO Improvement Proposal (BIP) process

Currently there is no formal process for proposing improvements for BAO, what level of participation is required to make a vote binding, or what power the team has to over ride a vote and what that would look like.

The BIP process discussion has spent over a week in #concepts where responses have been positive, so we have moved it to the governance proposals section of the forum in preparation for creating a snapshot vote where the intention is to have a “for” or “against” vote.

BIP process

  • There is no minimum number of BAO required to follow the steps to add a proposal
  • You should develop a concept/ proposal in the #concepts section of the forum.
  • After 1 week you can request a moderator to add it to the #governance-proposals section.
  • Moderators will check that the proposal has all the detail required, including any data, models and explanations of methodology used needed to fully assess the proposal. This is an important step that will allow “galaxy teams” to have confidence they can implement changes voted on without ambiguity or to avoid disputes resulting from miscommunication. Moderators will not filter proposals based on their views on the proposal itself, just on whether it is fully formed or not.
  • The proposal should spend at least 1 week in #governance-proposals, where the community can review its final wording. After 1 week unchanged, it can be moved to snapshot for a vote. This can be done by requesting moderators to inform multisig (or maintainer galaxy before multisig is implemented) that it is ready for voting.
  • Multisig holders (or the maintainer galaxy before multisig is implemented) can bypass this process and put up a vote straight to snapshot where a change is deemed time sensitive.


  • Quorum requirement is 10b votes. When a vote does not receive 10b BAO voting on its outcome, it will be left to the judgement of multisig holders (or maintainer galaxy before multisig is implemented) on whether to implement the change or not.
  • It is the responsibility of the party(s) proposing the change to promote and gather support for it in order to meet quorum
  • Multisig holders (or core team, before multisig is implemented) can veto a vote. When this happens it will automatically go to a revote within 4 weeks, where 25% of voting power and a majority of 2/3 is required to overturn the veto.
  • In the event of a veto, the team will create a forum post explaining their reasoning and give at least 1 week for opposition to the veto to make their points and for both sides to gather support for the revote.

Veto’s are intended as a safety mechanism for multisig holders, who are voted on, to prevent changes to the project that are damaging to its future.