Motivation

Since I've been in DAO since mid-2022, I've witnessed the evolution of Gearbox DAO products related to operational maintenance of the protocol. Despite the fact that the protocol itself is completely on-chain and completely autonomous, it is necessary to develop a number of internal products responsible for monitoring, data collection, and delivery of changes. These products are hidden from the eyes of ordinary users, but they play a significant role - they increase the security of the protocol, simplify the process of testing new versions and updates, and control the process of deploying changes (and decrease time to market!). I will give just a few examples of such internal products:

https://anvil.gearbox.foundation/

Service that enables rapid development and testing of new features. It automates creation of new forks, deployment of new contracts, generation of reports and visualization of new features and running integration tests on new chain state.

https://risk.gearbox.foundation/

Service for monitoring of both on-chain and off-chain events related to gearbox protocol.

sdk-gov

SDK provides abstractions to assist developers with interacting with the Gearbox smart contracts in a Typescript/Javascript environment (e.g. websites, node scripts, liquidators etc).

With the growth of protocol metrics, the scope of such products is only expanding, so I propose the creation of a separate initiative for such tasks. This initiative will be focused on building products aimed at monitoring, collecting and processing data. Data processing will include analysis and monitoring of unusual behavior, analysis of risk metrics, etc. Using such a data-driven approach will increase the reliability of the protocol as a whole.

Initiative configuration

The team consists of three full-time initiative contributors:

Position	Cost per Unit, $	Unit
Initiative Lead	8,000	1
Senior Fullstack developer	8,000.	1
Analyst/Researcher	4,000.	0.5-1

Budget

20k$/monthly* compensation and the corresponding amount in $GEAR depending on their multiplier choice, determined using a system of multipliers from GIP-43. At the same time, the Initiative Lead is capable of determining when OBRA begins to be applied to other subDAO members (perhaps some will just work as outstaff, for others a test period will be required etc). Additional 10k$/yearly budget for HR expenses. Out of this, the finder fee to an external unrelated platform will have to be paid for securing new members for this initiative. This is typically referred to as the finder’s fee in HR. It is assumed that this initiative is automatically extended if there is no separate vote on its adjustment. This initiative, like a few others, rolls into the new cycles unless discontinued.

Legal Agreement

Contributors within this initiative, as well as other initiatives, can, if necessary, sign legal agreement with Gearbox Foundation. The entity name/signators and other parameters contributors/Initiative leads can specify directly with Gearbox Foundation. That specifically includes the recently requested smart contract initiative by DLTXperts change of name while keeping the initiative as is: DLTXperts Ltd to DLTXperts Limited as a grantee.

Voting

Simple Approve/Reject