Authors:
Bruno Rodrigues, Count Vidal, Cozeno, DioDionysos, Face Shaver, Meertitan, Pavel
Summary:
Elect seven Optimistic Approval (OA) members every six months, starting in January. Request 126,000 TRIBE per six months from the DAO to compensate OA members.
Motivation:
OA has been one of the cornerstones of decentralization for Fei Protocol. This proposal aims to properly elect 7 OA seats, with a transparent and just compensation system in place. OA compensations will be folded into Tribal Force once it is established.
Specification:
- Conduct an approval vote on Snapshot with all the applicants to assign the 7 OA seats. The 7 members with the most votes will be part of the OA multisig.
- Transfer 126,000 TRIBE from the DAO treasury to the OA multisig.
- Hold OA elections twice every year, in January and July.
Every community member is welcome to make a case for their inclusion in OA. Feel free to nominate yourself as well as others.
OA members will need to be highly engaged and follow the discussions around the protocol. They will need to be aware of the FIPs that are part of the OA framework. OA members are responsible to ensure transparency in all OA actions.
OA is authorized to act according to snapshot results with the following scope: managing TRIBE rewards, deploying and removing minted FEI in lending and Laa$ integrations, tuning FeiRari parameters. For more info about the FIPs related to OA scope, click here.
As a part of their tasks, we propose the following operational framework:
-
All discussions pertaining to the operation and procedures of the OA must be done in the public Optimistic Approval Channel of Discord.
-
Any prospective transactions wishing to be queued up for consideration by the OA must be presented in the discord “OA” channel for a 24 hour discussion period. The presented transactions can be divided into two types, Direct Authorization or Subsidiary Authorization.
-
Every Subsidiary Authorization will be tracked by being assigned a homogenized sub FIP number when it presents itself for consideration. For example, new LaaS allocations that didn’t go through a separate snapshot can be named as FIP-36 (this is the empowering snapshot)-A/B/C (subsidiary number assigned based on order).
-
After determining that a new transaction is indeed empowered by an FIP, or is viable as a Subsidiary Authorization, the proposal may be queued up to the multisig.
-
Upon successful execution of a transaction, the original transaction exposition, along with a brief summary of what was ultimately executed, should be uploaded into the Optimistic Approval Tracker in Notion for transparency.
For more details about OA operational procedures, click here.