TL;DR
Yearn already operates a mature internal risk framework (ySec / Curation scores on curation.yearn.fi). This temp check explores whether the community wants a complementary, independent risk layer surfaced on the public front-end for depositors and via an institutional dashboard for contributors (curation, security, strategists), without replacing Yearn’s own scoring or governance process.
If there is appetite, the next step would be a scoped pilot (read-only API integration + optional org dashboard), not a binding spend commitment.
Context
From the 2025 recap -gov.yearn.fi/t/yearn-2025-recap-letter/14587: Yearn Curation grew to ~$150M TVL on curated Morpho vaults with explicit risk tiers, and the team emphasized that users value transparent risk frameworks over novelty.
Yearn’s Curation Risk Score Framework (11 factors, strategy + external protocols, documented here) is the right source of truth for Yearn-managed vault and strategy approval.
What we are not proposing: replacing ySec, overriding curation scores, or automating vault listings from a third party.
What we are exploring: whether an independent assessment of external protocols and venues (Morpho markets, Aave, Spark, Curve, etc. the same dependency surface your framework already scores) helps depositors and contributors compare and monitor risk faster, especially as Curation scales across chains.
Motivation
- Depositors on the public app often see APY first; external protocol risk is buried in docs or curation JSON, not always visible at decision time on the vault page.
- Contributors (curation, security, strategists) already triage external deps manually; a shared monitoring dashboard (wallet / vault exposure, alerts, incident feed) could reduce coordination overhead when re-underwriting after incidents (e.g. oracle failures, contagion events, themes raised in recent forum threads like Silo / xUSD context -gov.yearn.fi/t/what-is-the-status-of-silo-lender-arb-usdc-e/14572.
- Independence: a second opinion on venue-level risk (not Yearn strategy implementation) can strengthen trust without conflicting with internal scores, similar to how Immunefi complements audits without replacing them.
Proposed scope (if temp check passes)
A) Front-end (read-only, complementary)
- Display independent protocol / vault risk signals alongside existing Yearn curation data on vault detail pages (clearly labeled: “Independent by Philidor” vs “Yearn Curation”).
- No write access to vault config; no automatic listing changes.
- Data via public REST API -api.philidor.io — read access without API key for exploration; production integration subject to rate limits / partnership terms.
B) Internal contributor dashboard
- -dashboard.philidor.io: org workspace for Yearn contributors:
- Register EVM addresses (treasury, strategists, test wallets, curator ops).
- Visualize risk levels and vault exposure across protocols in Philidor’s coverage.
- Alerts feed for incidents affecting watched vaults / protocols.
- Intended for ySec, Curation, and vault ops—not end-user custody.
C) Coverage alignment
Philidor currently scores 700+ vaults across Morpho, Aave, Spark, Yearn, Beefy, Compound, Euler, Uniswap, and Sky methodology -analytics.philidor.io/methodology.
If Yearn strategies touch venues outside this set, we invite the team to review our public coverage map and discuss extending assessments to protocols that matter for Curation, before any front-end commitment.
What Philidor is (disclosure)
Posted on behalf of Philidor Labs -philidor.io, institutional DeFi risk infrastructure: deterministic Vector Framework (0–10), public API, Analytics, MCP for agents. We score Yearn vaults in our index today; this proposal is about complementing Yearn’s own curation UX, not competing with it.
Example: how independent scoring appears today (Yearn vault)
Philidor already indexes Yearn V3 vaults using the same public methodology as other protocols in our coverage. This is illustrative only, not a recommendation to change Yearn Curation scores or vault parameters.
Vault: USD yVault (Ethereum -analytics.philidor.io/vault/ethereum/0x696d02db93291651ed510704c9b286841d506987
0x696d02db93291651ed510704c9b286841d506987
| Signal (Philidor, independent) | Value |
|---|---|
| Overall | 8.41 / 10 — tier Prime (≥ 8.0) |
| Asset risk | 9.3 — USDC 100% |
| Control risk | 9.0 — 7-day timelock · immutable config |
| Platform & strategy | 6.1 — audits (ChainSecurity, Statemind, yAcademy) · strategy complexity “Fair” · 2 external deps |
Snapshot context at index time: ~$11.5M TVL, ~4.5% APY; on-chain events (e.g. DebtUpdated) surfaced in the events feed -analytics.philidor.io/events for operational monitoring.
How this could surface on Yearn’s front-end (pilot mock):
Yearn Curation risk level: [from -curation.yearn.fi]
Independent (Philidor): Prime · 8.41/10 → details
Depositors see two labeled signals: Yearn’s internal curation score (source of truth for listing) and an independent venue/strategy assessment for cross-checking. Contributors could watch the same vault—and treasury/strategist addresses—via -dashboard.philidor.io (alerts, exposure, tier changes) without replacing ySec review.
Methodology: -analytics.philidor.io/methodology · open API: GET /v1/vaults/{network}/{address}
Non-goals
- Replacing the Curation by Yearn scores or ySec workflow
- Governance votes driven by external scores
- Solana / non-EVM coverage in v1 (dashboard is EVM
0xaddresses today) - Paid integration commitment in this temp check, pilot terms would be a follow-up RFC if interest exists
Open questions for the community
- Is independent venue-level risk useful next to Yearn Curation on the public vault UI?
- Would ySec / Curation use a shared monitoring dashboard for addresses and incident alerts?
- Which external protocols in active Yearn strategies are missing from independent coverage today and worth prioritizing?
- Preferred integration surface: vault page badges, API webhook to internal tools, or dashboard-only pilot first?
Suggested next steps (if “Interested” wins)
| Step | Deliverable | Timeline (indicative) |
|---|---|---|
| 1 | 30-min call with Curation / ySec / front-end | ~1 week |
| 2 | Read-only API mock on 2–3 flagship vault pages (staging) | ~2–3 weeks |
| 3 | Contributor dashboard org + 3–5 watched addresses | parallel |
| 4 | Community RFC: scope, labeling, maintenance, optional grant | after pilot feedback |
Poll
Should Yearn explore a pilot for independent risk scoring (front-end surfacing + contributor dashboard) as a complement to internal Curation scores?
- Yes — interested in a scoped pilot (front and/or dashboard)
- Yes — dashboard / contributor tooling only (no public front-end yet)
- Yes — public front-end only (no dashboard)
- Not now — internal curation is sufficient (please say why in replies)
- Need more info — happy to discuss coverage gaps and methodology first
Happy to answer methodology questions, share more documentation, or run a short demo for Curation/ySec. If this temp check shows no appetite, we will not pursue integration further.