Every lending protocol the platform ingests has a page under
Tracking, and every page shows the statistics that matter for
its model. Pool lenders and vault systems do not have the same interesting
numbers, so there is no single template: Aave gets a health factor
distribution, Maker gets collateral composition, Compound gets absorptions.

The tables below are read from the tracking registry when this page renders,
so a protocol that ships is listed the same day, and a protocol we have not
built stays under “Planned” rather than being implied by an empty list.

Four models

  • Pool lending (Aave V3 and its forks): supplied and borrowed per reserve,
    the health factor distribution, at-risk debt, liquidations with the realized
    and configured bonus. See health factors and
    liquidations.
  • Vault / CDP (Maker): vault count and size, collateralisation by collateral
    type, the composition of what backs the stablecoin. See
    Maker.
  • Single-asset markets (Compound v3): one borrowable base asset per market,
    and absorptions, where the protocol takes the debt rather than a liquidator.
    See Compound v3.
  • Isolated markets (Morpho Blue): one collateral, one loan asset and one
    oracle per market, with bad debt written off against that market’s suppliers
    alone. See Morpho.

Coverage

Live

Protocol Model Chains On its page Datasets
Aave V3 pool lending eth_mainnet Health factor distribution; Accounts closest to liquidation; Per-account composition; Liquidations with realized vs configured bonus aave_liquidations, aave_health
MakerDAO vault / CDP eth_mainnet Collateral composition over time; Concentration (effective N); Vault creation activity maker_vaults
Spark pool lending eth_mainnet Health factor distribution; Accounts closest to liquidation; Coverage and known exclusions; Liquidations with realized vs configured bonus aave_liquidations, aave_health
Compound v3 single-asset markets eth_mainnet Absorptions and collateral seized; Breakdown by market and month compound_absorbs
Morpho Blue isolated markets eth_mainnet Liquidations that left bad debt; Per-market losses in the market’s own tokens morpho_liquidations

Planned

Protocol Model What it needs
Euler v2 isolated markets Vaults that can borrow from each other: risk chains rather than one pool
Fluid pool lending Lending and DEX liquidity sharing the same collateral

A dataset listed against a protocol is one whose export form offers that
protocol as a filter. Rows exist only where the pipeline could compute them:
the health panel, for instance, is built only for deployments whose oracles
are replicated exactly, which is why Spark has liquidations and no health
factors (Aave forks explains the rule). Every column of
every dataset is in the data dictionary, and the
methodology page says how each number is derived.

What “live” means

Live is a standard, not a label: the contract math has been replicated and
validated against the chain before anything derived from it is published, the
extraction runs on a schedule, and the page’s figures come from the warehouse
rather than from an estimate. A planned protocol has none of that yet, and its
row says what it needs. Suggesting a protocol is a matter of opening a
conversation with staff, who keep a registry of candidates and how much of the
existing pipeline each one would reuse.