Yvusd monitoring
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 13
- Forks
- 13
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Description
Some ideas on alert triggers:
- when unlocked APY is higher than locked APY for more than X hours
- when APY on a strategy is negative
- when CCTP bridging delays happen (can check time between sending and receiving funds)
- when flashloan liquidity drops below necessary level needed for strat unwinding
- if a cooldown request for a large amount of locked yvUSD is detected
For more info about yvusd check report: https://risk-score-mon7fd4hb-yearn.vercel.app/report/yearn-yvusd/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked yvUSD risk report and inspect the repository’s existing monitoring and alert patterns. Clarify which proposed triggers are required, define their thresholds and data sources, and confirm the expected alert behavior. Done means the selected yvUSD conditions are monitored with agreed thresholds and tested alert delivery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100