🗳️ Voting

Force Improvement Proposal (FIP)

A FIP is a proposal to signal or effect change to Force DAO’s governance or products. The objective for a FIP 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. FIP Template

  3. Accepting and rejecting FIPs

  4. Next Steps

1. Governance Process

  • Forum - All major discussions must start here in the form of a FIP. 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 multi-sig or through DAO vote will execute the proposal that garners supermajority support.

2. FIP Template

FIPs must follow this template:

  1. Name, scope, and objective.

  2. Categorize the FIP into one of the following: Emissions, Vault, Governance, New Product, or Other.

  3. Provide a low-level overview of the FIP.

  4. Provide high-level details of the FIP.

  5. Business and technical requirements of the implementation of the proposal.

3. Accepting and rejecting FIPs

  1. Once submitted, the FIP should be open for discussion for at least 5 days (assuming it is well-formed). The FIP 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 FIP 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 FIP. If there are changes necessary, they will synthesize/modify in a comment which will then be pushed forward to snapshot.

  4. If the FIP 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 signaled on the FIP 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 FIP is accepted, the Force 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 FIP process is a version of https://forum.badger.finance/t/about-the-bip-badger-improvement-proposals-category/20 which is a modified version of https://github.com/rust-lang/rfcs. The template also draws inspiration from forum.renproject.io