FIP Post Guidelines

Fei Improvement Proposals (FIPs) - Fei Protocol are the currently standing rules of FEI governance, With the passing of FIP-57, the following guidelines will compliment the above document:

  1. 48 hour last call before snapshot. The last call should be announced in the discord governance channel for publicity; enlisting the aid of a mod if need be.

  2. A notable exception would be technical rollouts, or routine contract upgrades such as FIP-48

  3. During the “Last Call”, each FIP should clearly state what every voting option would be. The last call post should also indicate any edits which have been made from the original due to the discussions in the forum. If the proposal is significantly amended during last call, the author should respect the flow of the discussion and delay the snapshot accordingly.

  4. Only the author(s) of the original forum discussion post should make the snapshot for that particular motion, or allow somebody else to do so with explicit written permission in that original thread.

  5. Upon the passing of a snapshot vote, the poster should announce the specific time they intend to forward the proposal for on-chain voting/Optimistic Approval. If a particular snapshot is a “temperature check” and not meant to be executed directly, it should be clearly indicated by its authors.

  6. Routine protocol upgrades can be exempt from these requirements.

  7. If a proposal outright fails, the author should indicate whether they intend to repost the FIP after editing its contents with community input. If the edited points required of the failed FIP does not exceed a majority of the original proposals, then the FIP may keep its original FIP number, add “FIP-xx amendment 1” to its title, and may proceed directly to last call. Though if the edits required were so substantial that a majority of the original proposals have been changed, the FIP number would be scrapped and it should restart from scratch on the forum.

  8. If a proposal passes, the authors should indicate if they like to make non-substantive edits as soon as possible, and outline every edit from the proposal that has passed the snapshot.

  9. The DAO guardian will veto votes if they satisfy any of the following criteria:

  • The proposer or payload is unknown.
  • Proposal which distributes PCV or incentives to voters on the basis of their vote (bribery proposals)
  • Proposals which add admin control to untrusted accounts
  • Any veto authorized by a TRIBE snapshot that reaches quorum and has at least 24 hours duration (mostly applicable to OA)
  • A proposal which contains a security vulnerability, either disclosed by core team or community member, and verified by any third party such as audit firms, security researcher, or community members.

Proposals that blatantly disregards these guidelines should be rapidly informed as such by community members. If the authors do not respond to valid inquiries of procedure, and outright circumvents governance practices, the proposal could be subject to sanctions such as non execution by OA approval, or veto by guardian/DAO.