External keeper/relayer not redundant
Meteora's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Dynamic Vault relies on the Hermes keeper (operated by Meteora) to rebalance allocations across lending protocols (Solend, Tulip, others). Documentation describes Hermes as rebalancing every few minutes, triggering the rebalance crank when allocation drifts >0.1%. No documentation confirms multiple independent Hermes instances, a permissionless fallback keeper, or an on-chain automated failover. If Hermes fails, Dynamic Vault stops rebalancing and vault funds remain static in last-allocated lending protocols (liveness risk for yield optimization). DLMM/DAMM v2/DBC do not use keepers in their swap path and are unaffected. Scored yellow: single keeper with no confirmed redundancy for Dynamic Vault.
Sources #
- DocsDynamic Vault Algorithm DocumentationHermes performs calculations every few minutes; rebalance crank triggered when allocation drifts >0.1%; no mention of multiple keeper instances or permissionless keeper fallbackretrieved 2026-05-16
- Meteora Dynamic Vault DocumentationDynamic Vault: Hermes monitors utilization rates and triggers deposits/withdrawals to/from lending platforms; safety mechanisms described as keeper-mediatedretrieved 2026-05-16
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →