Loading
Every change that moved a published figure or changed what it counts, dated, with what a reader who used the old one needs to know. Corrections are in the same list as everything else and are not marked more quietly.
A rendering fix, a new page or a faster query is not here however much work it was. What belongs is the small number of changes where the same question asked last month and today gives a different answer.
Each lineage block on the API reports the methodology version it was built at. Current: aspern-0.3. Versions this build can still produce: aspern-0.3, aspern-0.2. The list never shrinks — a published hash is a commitment, and it can only be re-derived if the version that produced it still builds.
The API answered `depositAsset` with whatever the source called the pool, which for Concrete and Lagoon vaults is the vault’s own share token: "CTDELTAWEETH" is the receipt, not the deposit.
What it means for a figure you already have. It now answers with what a depositor actually put in, read from the vault’s own asset(). The aggregator’s label is kept as `sourceAssetLabel` and the token address is published, so nothing has to price by ticker. Anything keyed on the old value for a Concrete or Lagoon vault was keying on a token nobody holds outside the vault that issued it.
/v1/vaults, /v1/vaults/{slug}
Scroll, Shape and Tempo added to the ERC-8004 registry read.
What it means for a figure you already have. Registration totals rose by 2,495 across 3 chains — Shape alone carries 2,098, more than Scroll, Taiko, Linea, Metis and Mantle together. Any registry figure quoted before this date is short by that much. X Layer is deployed and still unread: no public endpoint will serve the query.
/identity, /v1/agents/claims
Every measurement endpoint now carries a `lineage` block: source, chain, block, when it was observed, when it was computed, the methodology version, what it covers and what it does not.
What it means for a figure you already have. Nothing moved. Several fields are null on purpose — a vault read from a venue HTTP API has no block number, and writing the chain head there would invent a provenance.
/v1/lineage
The identity page led with pointers and unreadable cards summed into one figure: "63% carry no card anyone can read on chain".
What it means for a figure you already have. Now stated as three shares — 37% on chain, 49% a URI we choose not to follow, 14% neither. The summed figure was literally true and read as "63% have no metadata", when most of that is a pointer that very likely resolves.
/identity
The crowding event study published a control leg of 215,700%. One vault’s share-price series carried a bad point and a cross-sectional MEAN carried it into the published figure.
What it means for a figure you already have. The statistic is a median across vaults, an impossible cumulative return is refused, and every row publishes how many readings it refused. The answer changed from a spurious cost to “not distinguishable from noise”, which is what the data supports.
/crowding?view=cost
Two pages divided by the wrong denominator: agent-managed capital was reported against every vault we track, and survivorship counts from one venue sat beside all-platform capital.
What it means for a figure you already have. Agent-managed capital is about a sixth of the tracked total. Any share quoted from those pages before this date was too small by roughly that factor.
/money, /survivorship
The paywall became one switch with per-surface row limits, replacing two settings that disagreed.
What it means for a figure you already have. Some figures that had been reachable without a plan no longer are. Nothing that was published became wrong; less of it is free.
/pricing
A price matched to a denomination by TICKER matched an unrelated asset: a $74M vault denominated in vUSD was valued at $4.34.
What it means for a figure you already have. Such prices are refused rather than published, on the page and in the change feed — which would otherwise have announced the collapse of a stablecoin that never moved.
/assets
The registry sweep found the contract deployed on eighteen chains where the code claimed eleven and ingest read three.
What it means for a figure you already have. One unread chain held more registrations than every read chain combined. Every ERC-8004 figure published before this date was a fraction of an unknown denominator.
/identity
Vault denominations are read from the vault’s own asset() and the token’s own symbol(), rather than from an aggregator’s label.
What it means for a figure you already have. Stored from this date. The API kept serving the aggregator’s label until 5 September, which is the correction at the top of this page.
This page is what we changed. Us against other sources is where our figures sit beside the ones other people publish, with the reason each differs — including the one we cannot yet explain.