yearn-linear-gh-sync[bot]
yearn-linear-gh-sync[bot]
Currently we have our code for the various api endpoints in multiple repos: * `/v1` routes: [https://github.com/yearn/yearn-exporter/blob/master/yearn/api.py](https://github.com/yearn/yearn-exporter/blob/master/yearn/api.py) * apybot(kx9x): [https://yearnapybot.azurewebsites.net/api/chains/250/vaults/0x0DEC85e74A92c52b7F708c4B10207D9560CEFaf0/pps/1d](https://yearnapybot.azurewebsites.net/api/chains/250/vaults/0x0DEC85e74A92c52b7F708c4B10207D9560CEFaf0/pps/1d) * yearn-exporter-api (not published yet): [https://github.com/mariuspod/yearn-exporter-api](https://github.com/mariuspod/yearn-exporter-api) This has the following...
## Background APY data for all data is is [generated and published to S3](https://github.com/yearn/yearn-exporter/blob/master/scripts/s3.py). The data is consumed and displayed in various places, including [https://yearn.finance](https://yearn.finance) . It is critical this...
check if it's feasible to bump the python requirement to 3.10, which gives up pattern matching and some performance improvements. there were some incompatible libraries which have upgraded since *...
A high-level overview can be found here [https://docs.yearn.finance/partners/integration_guide#delegated-deposit](https://docs.yearn.finance/partners/integration_guide#delegated-deposit) Blocks [#193](https://github.com/yearn/yearn-exporter/pull/193)
goal is to catch deprecated and faulty strategies, to keep job strategies array healthy
the tldr: "make a github action to deploy and pin yearn.finance to IPFS every time the master branch gets updated via github action, vercel, or fleek we’re using AWS amplify...