What Cleaton covers, chain by chain
Every chain and venue class in the covered universe, with the accounting method committed per pool and the calibration stratum each is scored against. Coverage is published alongside accuracy, because accuracy on a hand-picked subset is a much weaker claim.
Aggregators report a level and incentive trackers report an expiry date. Both are necessary inputs and neither is a durability estimate: an expiry says when the subsidy stops, not how much liquidity leaves when it does, which depends on depositor composition and where else that capital can go. That is the part Cleaton is built for, across 36 surfaces carrying the same primitive.
Coverage, venue by venue
Baseline hazard is stratified by venue class, because a lending market with utilisation-dependent withdrawal availability behaves nothing like a constant-product AMM. Each entry says what is committed per class and where the estimate degrades.
Robinhood Chain
The subject. A new chain running concurrent incentive campaigns against dated expiries — the case the whole method was built for, and a public test of it.
Base
Where the registry and bond vault deploy first, because that is where consuming contracts are. Attestations about pools here follow the same committed method.
Arbitrum
The second contract target, for the same reason. A Robinhood Chain mirror comes after, once there is something to mirror.
AMM pools
Constant-product and concentrated-liquidity pools. Canonical liquidity is derived from reserves against a reference price.
Lending markets
Total supplied minus total borrowed. Withdrawal availability depends on utilisation, so exit friction carries more weight than in an AMM.
ERC-4626 vaults
Canonical liquidity is totalAssets(). The accounting function is committed in the signed payload before any outcome is known.
Staking contracts
Unbonding periods and withdrawal queues raise the exit friction term, which dampens how fast elasticity is realised.
Stablecoin pools
The class where reward elasticity runs highest, frequently between 1.5 and 4.
Covered or attested?
Covered means the ingestion and feature pipeline runs for a venue. Attested means a signed horizon is published for a specific pool within it. A chain can be fully covered while individual pools on it are declined: a pool outside the support of every calibration stratum gets an explicit OUT_OF_SUPPORT record rather than an extrapolated number. Declining to make a confident claim is a supported output, and those declines are published too.
Browse all 36 surfaces · read the method in https://dapp.cleaton.xyz/mcp
Publish a horizon. Get scored on it in public.
Durability attestation for autonomous capital. Every horizon is signed, dated, and published before the outcome is known — so it can be marked right or wrong later, in public.