Which readers ran and when, how much of what they set out to read they reached, where our figures disagree with somebody else’s, and what we refuse to publish rather than estimate. Everything here was already somewhere on this site; no page put it together.
There is no single quality score, deliberately. One number would average a stale venue against a refused price against an unexplained gap, and those three fail differently and matter to different readers. The components are here; the composite is not.
Three measurements taken separately, for different reasons, turned out to be the same finding: the parties who declare something and the parties who get paid are, in our reading, nearly disjoint sets. Each row carries the exact populations it compares, because the same question asked with a looser definition gives a different number and both are true.
| Two populations | One side | The other | In both | Measured over |
|---|---|---|---|---|
| Paid on a rail, and a vault we read | 3,380 | 3,797 | 0 | Addresses ever paid for a SALE (the recipient lists a price in a catalogue we read) against open vaults, matched on the vault’s contract address. |
| Holds an ERC-8004 registration, and runs a book | 564,898 | 472 | 0 | Distinct registration owners against operators carrying an on-chain address, matched case-insensitively. |
| Declares a callable endpoint, and has been paid | 2,895 | 3,380 | 11 | Owners declaring any service kind (MCP, A2A, OASF, web, wallet, social, x402, other) against the paid addresses above. /work asks a looser version of this question (MCP and A2A only, any incoming transfer counted as paid) and answers 15 of 1,287; both are true. |
This is what we can see, not what exists. One firm can run both sides under addresses that never touch, exactly as one owner can fund payers that never pay each other. No link is visible; that is not the same as no link.
in-line, beating and short are the sharpest thing said here about a vault: what a holder actually earned against what the venue advertises. A verdict drawn from a price that moved once is arithmetically right and describes nothing that will happen again, so this is how many of them are which. Counted over the 417 open vaults whose realised return can be compared with an advertised one at all.
| Verdict | Vaults | Movement spread | One step explains it | Series barely moved |
|---|---|---|---|---|
| in-line | 362 | 353 | 1 | 8 |
| beating | 29 | 25 | 1 | 3 |
| short | 26 | 17 | 5 | 4 |
One step explains it: enough intervals moved to judge, and one of them still carries most of the window: a correction, or a fee taken in one go. Series barely moved: most of the movement sits in one interval of a price that hardly moved at all, which is a thin reading rather than a step we can account for. The two are never added: only the first is a thing we can name. Every vault says which of these applies to it in the cannotSee field of its own check.
A realised return missing a component is not a smaller return. It is a different measurement wearing the same name, and which way it is wrong depends on which component is missing. Counted over the 2,616 open vaults holding capital, $11.44B between them.
| Component | Vaults | Share | Capital behind it | What it means where it is missing |
|---|---|---|---|---|
| A value series at all | 2,546 | 97% | $11.28B | Without one there is no realised return to state, and the vault is absent from every return figure rather than counted as flat. |
| Profit stated by the venue | 1,708 | 65% | $273.35M | The venue’s own profit series. Where it is missing the return is reconstructed from value alone, which cannot separate a deposit from a gain. |
| Share price | 838 | 32% | $11.00B | What one share was worth. It is the only series that survives deposits and withdrawals untouched, so a vault without it needs flows read correctly instead. |
| Funding paid or received | 251 | 10% | $129.88M | For a perpetuals book, funding is often most of the result. Absent, the return is right in total and says nothing about where it came from. |
A size read two days ago is not wrong; it is old, and the difference matters to somebody sizing an exit. A venue is called stale here after 36 hours.
| Venue | Vaults | Median age | Stale | Capital behind them |
|---|---|---|---|---|
| 227 | 0.7h | 0 | — | |
| 164 | 0.7h | 0 | — | |
| 31 | 0.7h | 0 | — | |
| 25 |
Every figure is as old as the reader behind it. These are past twice their own interval, or a quarter of an hour where that is longer, so anything resting on them is older than it should be. A reader that runs weekly and completed two days ago is not here, which is the point of measuring against its own schedule rather than against a flat day.
Four questions asked of this site every six hours, each with an answer that does not share an input with the figure it checks: the published size of the largest vaults against the contract’s own quantity at an outside price, identity registries against their own id sequence, readers that succeed and get nowhere, and registers whose published count has not moved while vaults wait. A failing answer reaches the operator the same way a stuck reader does.
Last asked 19 minutes ago.
59 of 59 largest vaults pass the ±25% sanity check, 0 fail it; tighter: 58 within 1%, 59 within 5%, 1 could not be asked
20 chains, 824,628 identities held, 0 chain(s) with a hole larger than 1%
How much of each thing we can actually see. Five separate questions with five separate populations, so the percentages are not comparable with one another and are never added up. Where capital is missing, the largest venues it sits on are named.
| What | Share | Seen, of | Largest gaps |
|---|---|---|---|
| Perp-vault capital whose open positions we read in the last three daysPopulation: open perpetual-venue vaults with a size. Capital, not notional: a vault counts by its equity, however levered its book. | 35.4% | $96.28M of $272.27M | Hyperliquid $174.16M (62) · dYdX $1.83M (0) |
| Position notional in a market whose open interest we hold, so a crowd can be sized against itPopulation: gross notional of the positions we read, per instrument. Notional over notional. It is never divided by vault capital, which would let a levered book inflate the figure. | 2.2% | $175.21M of $7.97B | venues that publish no open interest |
| Lending capital whose collateral we can see throughPopulation: open lending vaults with a size. Includes vaults that lend nothing, read as such from their own totalBorrows(). | 99.8% | $8.78B of $8.80B | Euler $21.42M (30) · Morpho Vaults V2 $487.7k (3) |
| Capital whose manager we can name as a firmPopulation: open vaults with a size. A firm, not a row. Venues create an operator per venue, so the same manager can appear several times; this counts capital joined to one firm record on evidence that is a domain or a key, never a resemblance between names. |
Several figures here are also published by somebody else, and several of them differ. Each comparison carries an explanation or is marked as not having one.
These counts are a measure of honesty, not of coverage. A vault whose underlying we cannot price is published as unvalued rather than estimated. Reading the number below as a failure is the one misreading this page exists to prevent: the alternative is not a better figure, it is a made-up one.
aspern-0.3
Every published figure carries this version in its evidence block, and every assessment document is hashed under it. A figure computed under an older version stays checkable: this build can still produce the versions it has published.
How each figure is arrived at · what changed and when · the independent check
| Incentives and rewardslower bound |
|---|
| 681 |
| 26% |
| $10.62B |
| A reward rate the venue publishes. Where it is unread, the realised return we state is a LOWER BOUND: the holder received that and something else we did not count. |
Every row is a count of vaults for which that series exists, never an estimate of how much the missing part would have been. A gap reported as a number would be the invention this table exists to prevent.
| 0.7h |
| 0 |
| — |
| 215 | 0.7h | 0 | — |
| 4 | 4.5h | 0 | — |
| 322 | 0.0h | 0 | — |
| 59 | 0.7h | 0 | — |
| 4 | 3.1h | 0 | — |
| 1 | 0.7h | 0 | — |
all 1 listed URL(s) of ours quote their price, 1 checked against the catalogue's own figure
181 jobs judged against their own history, 0 spinning
183 jobs with two finished runs and a published ceiling, 0 over it twice running
0 identity/identities span several addresses, every one on a stated basis that is not the name
1 venue name(s) held by more than one platform row, 0 of them carrying vaults
1 population(s) still draining; every other uncovered row carries a reason
882741 stored group(s) across 1839 seller(s), and every seller's stored count and largest group match the two figures published beside them
across 1176 address(es) every phase split sums to its job count, every evaluator split sums to its completions and every supplier split sums to its recipient count; 0 completion(s) were evaluated by the provider itself and 6919 by nobody
nothing has been refused for a bad signature; 4 refusal(s) for anything else, which is what a public URL attracts
no venue trade is stored more than once, which the key no longer promises and the venue’s own timestamps are why it holds
1 index(es) exist on the server and in no file, 0 MB between them. A schema change drops them and nothing reports it; the jobs that used them just get slower.
18 compressed chunk(s) hold 270 MB of index over zero rows. REINDEX TABLE on each one returns it in about 100ms each and reads nothing differently; it takes a lock, so pick the moment.
74 table(s) over 64 MB and none doubles inside 120 days
seven families with no retention, 72.1 MB between them over 70 day(s), the largest heading for 207.2 MB in a year
no contract is held as more than one open vault, and 2 settled duplicate(s) carry no capital reading of their own
archiving is current, pg_wal holds 0.5 GB
832 vaults carry an outside reading; of the 388 whose size we read from the chain ourselves ($9209M), none disagrees with theirs
1341 readings for 2026-10-20, and no day has fallen against the one before
92 vaults waiting across 3 registers, 0 register(s) unmoved in 7 days
| 66.3% |
| $7.58B of $11.44B |
| Concrete $1.23B (31) · Morpho $1.04B (62) · Morpho Vaults V2 $498.21M (77) · ether.fi Liquid $374.43M (4) · Lagoon $114.84M (59) |
| Strategy-vault capital whose deployed contracts it names to usPopulation: open strategy vaults with a size. The contracts, not the amounts in them. Those are bespoke per protocol and are not read, so this says what a vault is exposed to and not how much. | 52.3% | $1.23B of $2.36B | ether.fi Liquid $374.43M (4) · Lagoon $114.84M (59) · Veda $107.44M (4) · Avant avUSD $100.71M (1) · Ember Protocol $77.34M (25) |
| Capital with a reading of what could be withdrawn nowPopulation: every open vault with a size. Lending vaults from market liquidity, perp vaults from the venue’s own withdrawable margin in the last three days. | 79.3% | $9.07B of $11.44B | Concrete $1.23B (31) · ether.fi Liquid $374.43M (4) · Lagoon $114.84M (59) · Veda $107.44M (4) · Avant avUSD $100.71M (1) |
| Capital whose control (owner, roles authority, proxy admin) we have readPopulation: open vaults with a contract address on an EVM chain. Read is not safe: a reading says who can change the vault, not that nobody can. | 98.2% | $11.07B of $11.27B | Concrete $50.43M (6) · Euler $27.04M (162) · YieldNest $24.02M (9) · Hyperliquid $22.62M (294) · Morpho Vaults V2 $20.60M (67) |
Computed 30 minutes ago; positions as of 2026-10-20 11:33 UTC.