Venues

Coverage describes what a venue's data can support once its ingestion is running; `status` says whether anything is ingested yet. For a venue with observable own-state — an on-chain venue, resolved and read directly — status "registered" means resolved and awaiting ingestion, and such a venue publishes no figures whatever its coverage says; "unresolved" means named in the venue universe but not yet resolved, a declared gap rather than an omission. The posted and corporate classes do NOT resolve on-chain and are not described by that vocabulary: CeFi desks publish through cefi_credit_rates and corporate issuers through the corporate stack, so those venues can and do publish figures while carrying status "registered" — for them `coverage` and `validated` are the authority and `status` is not. Read the fields together or not at all. Each axis's `level` says what is observed and its `reason` says BY WHOM (operator; 2026-10-01): `full` where the venue's own contracts are read for that axis, `partial` where a figure is observed but only through an intermediary or in part — most often the aggregator (DefiLlama), whose rows are its report of each pool, not a read of the venue — and `none` where nothing is observed now. Each axis additionally carries `validated`: whether what has been ingested has passed a verification gate against a second observer. It is a THIRD question. An unvalidated figure is published with its observer named on the figure itself; it is not withheld, and it is not a validated one.

A family is the presentation parent of a venue: one protocol across its chain deployments (Aave v3 on Ethereum, Arbitrum, Base…), one corporate issuer, or one desk. family_id matches the ids other payloads use (the corporate issuer_id, the rate-card desk key). It is NOT a measurement unit: every figure in this dataset keys on venue_id, and a family lists its venues rather than summing them. Deployments of one family are separate contracts with separate books and can differ in collateral, parameters and risk.