A vault that tells you who is running it.
Every yield vault depends on an account that calls report()
on a schedule. Warden publishes that account, bonds it, and slashes the
bond when it misses a watch. Today the address is anonymous —
live vaults on Base run on
keys, and one of them is behind
.
Depositing and withdrawing are live — the app runs against ERC-4626 vaults already deployed on chain. The bonded keeper and private routing are not built, and are marked wherever they appear.
The snapshot failed to load — figures will read “—”. Serve over HTTP;
file:// blocks the fetch.
The keeper is walking.
- Coverage lost
- 0.0%
- Watches walked
- 0
- Since last row
- 0s
Six pages, and a working app.
Depositing and withdrawing are live. Two features are not built and say so.
Three rails
The vault, the share token and the bond. Two of the three work today.
02 — FlowDeposit to redeem
What actually happens on chain when you put money in and take it out.
03 — Private tradingNot built
Batched execution so your size is not a public signal. Design intent only.
04 — How it worksThree steps
Connect, deposit, redeem whenever. All three are live.
05 — AccountabilityWhy build it
Measured on chain: how few keys actually run the vaults people use.
06 — The appUse it
Connect a wallet and move real money. Start with an amount you can lose.