yearn / budget

yearn budget requests and audits
MIT License
36 stars 26 forks source link

Funding yDaemon Team #106

Closed Majorfi closed 1 year ago

Majorfi commented 1 year ago

Scope

yDaemon is an API, written in go, to provide an easy access to processed data from Yearn's ecosystem. It's now used in various projects and is becoming a milestone for our products:

yDaemon provide us with a full scale API, ready to compute various elements, from the vault list, to the harvest, from the prices to the meta elements and much more. A full documentation is available here: https://ydaemon.yearn.farm

While relying mostly on the subgraph with the V1, we are now trying to bring a new version which would use mostly (target 90%) a direct connection with a set of node to compute the relevant data. The idea is to be able to bootstrap yDaemon in a few minutes, grab all the stuff we need to at least mimic what we have from the subgraph, while bringing more customisation, more routes, more.

Scope includes:

Plan

The API will evolve with our needs, but here are some stuff we plan to work on

Deadline

2023-02-27

People

Possible contributors:

Money

We would like to request a 9000 DAI grant for a 3 month initial period which will be used to pay contributors. We plan to distribute a grant for each person in charge of a project and use bounties to fund other contributions linked to projects in maintenance mode or isolated contributions.

Amount

9000

Wallet address

0x0

Reporting

Monthly

kyhoon commented 1 year ago

Monthly Report for yDaemon - December

The experimental branch has been merged to the main branch, and furthermore, the indexers for vaults and strategies have been implemented. As mentioned in the above request, we plan to provide the historical APY and the breakdown of earnings for a given vault/strategy from the indexed events. To this end, we started with adding a simple pricing system using external APIs.

Many other PRs were done this month to maintain the data integrity of yDaemon, namely the risk framework and the metadata of strategies and vaults. We share some examples of these maintenance efforts in the following.

Risk Framework

We discovered that there are a number of discrepancies in our perception of the risk scores and the actual rubric (e.g. high scores for Curve and Balancer pools), which kept us from adding the risk scores to the new frontend. They will be handled together with the missing scores (e.g. StrategyCurveyCRV) this month.

Metadata