Platform

Known limits

Being explicit about limits is consistent with the whole thesis. Every product has them; few write them down.

Nine servable types. token.price (5 providers, anchored) and spot.price (4 providers, consensus) are the two that reach past a single source. perp.price, funding.rate and futures.open_interest carry three, three and two venues, and are still capped at single_source, for the reason in the next paragraph. solana.sol_balance, solana.token_risk, defi.protocol_tvl and tiktok.profile are single_source. Everything else is roadmap.

More venues is not more observers. Three exchanges reporting their own funding rates are three quantities, not three observations of one quantity, and no number of venues will lift that cap: it is a property of what the number is. Only where the venues are pricing the same asset, as in spot.price, does agreement between them mean anything, and that is the one type where consensus is reachable today.

Independence is never measured, at any number of sources. Pairwise dispersion cannot separate the shared component from the private ones: at three sources the system of equations is exactly determined and has no residual to test, and the covariances stay unidentified however many sources are added. So independence is reported as assumed, not_refuted or refuted, never as a measurement. A test that could have refuted it and did not is the honest ceiling.

What verification cannot catch. Two colluding sources that read the same upstream, in a type without an anchor, are indistinguishable from the truth, which is why that datum is labelled single_source rather than consensus. Even an anchor that agrees is not automatically an independent check: when the feed aggregates centralised venues and the answering source is one of them, the trace says so instead of claiming independence.

Roadmap, not present. The pieces marked roadmap here and on the token page do not exist yet and are never described in the present tense.