The vault doesn't earn.
A keeper does.
An ERC-4626 vault produces nothing on its own. An ordinary account with a
private key calls report() on a schedule, and that is what
compounds the yield. Across
vaults on Base I counted
such keys — and
of those vaults
depend on one of them.
Every figure here is read from public RPC with no API key, and the panel re-runs the same query in your browser.
The snapshot failed to load — figures will read “—”. Serve the site over
HTTP; file:// blocks the fetch.
The keeper is walking.
- Coverage lost
- 0.0%
- Rounds walked
- 0
- Since last row
- 0s
Six pages, one argument.
Each one is a separate measurement. The last lets you reproduce all of them.
reports
Every keeper call in the window, and the three numbers that come out of it.
02 — The keysaccounts
Who paid for those calls. All of them plain EOAs, and the blast radius of the largest.
03 — Cadencemedian
What a schedule looks like, and what the tail looks like when one slips.
04 — Silencesworst
The longest any vault went unattended. Nothing reverted; it just stopped compounding.
05 — Re-run itCheck me
The same query, against Base, from your browser. No key and no server of mine.
06 — MethodAnd its limits
How it is measured and the three things the instrument cannot see.