Loading…
Coverage & Scope
What CantonCap Covers
Which venues, markets and assets appear, and how that is decided.
A venue is covered once a connector reads it. Each connector is written against the venue's documented interface, its capabilities are recorded method by method in the connector descriptor the matrix below is drawn from, and its records are published only where their scope and the source's terms allow anyone to see them. A venue whose data is visible only to an integrator credential or an entitled party contributes no public figure.
A market is covered when a covered venue lists it and the API publishes it, and an asset appears when a covered venue trades it or an approved registry names it. Every market is filed under one of four categories: AMM, CLMM for a pool with concentrated liquidity, order book, or hybrid.
The matrix lists every venue the API publishes markets for. A venue that is documented but not yet connected, or that waits for a partner agreement, joins it when it publishes its first market.
Coverage can differ from one figure to the next. A venue may publish prices but no trades, candles but no book, or a reported volume that does not yet reconcile with its trades and is kept out of every total. Each figure states how much of its population it covers, in the terms below.
Visibility Scope
Who was able to observe this record on Canton.
Public market
Observable on a public venue and publishable to anyone.
Caller visible
Visible only through the specific integrator credential that observed it.
Party scoped
Visible only to an explicitly entitled Canton party.
Unknown
Scope could not be established, so the record is never published.
Pipeline Stage
Where in the pipeline a data-quality finding was raised.
Source
Raised while reading from the venue itself, before any interpretation.
Normalisation
Raised while mapping a venue's payload onto the canonical model.
Calculation
Raised while deriving a published figure from admitted observations.
Stream
Raised on the live delivery path rather than in stored data.
Dependency
Raised because something this stage relies on was itself unavailable.
Coverage Completeness
How much of the relevant population contributed to a derived figure.
Complete
Every venue known to trade this instrument contributed.
Partial
Some venues that trade this instrument did not contribute to this figure.
Sampled
Built from a bounded sample rather than the full population.
Accumulation only
History begins when CantonCap started observing this source; earlier periods do not exist upstream.
Unknown
Coverage could not be determined for this figure.
What Each Connector Can Answer
The seventeen canonical connector methods, across every venue with a market, from the connector descriptor the API team maintains. The mode is a provenance statement, not a quality ladder.
Each cell says how a method is answered: reported by the venue itself, computed by CantonCap from what the venue does report, answered without calling the venue, or not offered. Available means the venue's documented interface supports the method; whether the venue is answering right now is the stamp beside its name, and the status page.
