CLARITY Compliance: Verifiable Liquidity and Trading Data
An institutional trader sizing a position in a digital asset is looking at the same question on every venue: how much can move at what price, and what's the execution cost of moving it. The answer determines whether the trade gets routed through a centralized exchange, a DEX aggregator, an RFQ network, or some combination, and how it gets split across them. The answer also has to be defensible after the fact, when best-execution reviews and risk committees look at why the trade was routed the way it was.
The data behind that answer comes from several places: venue-published order book snapshots, aggregator feeds, AMM curve calculations, and historical execution data that traders' own desks have collected. Each source is doing useful work. None of them, on its own, produces a record an institutional desk can verify directly against the markets it traded in.
Liquidity reported, not proven
Centralized venues publish order book data and trade tapes through their APIs, and institutional desks consume those feeds for sizing and execution analytics. The feeds are reliable in normal conditions, and they are also the venue's own report of its own activity, with no external mechanism to confirm that the depth shown reflects the depth that was actually accessible at the moment a trader needed it.
Onchain venues offer a different problem. Liquidity in an AMM is mechanically visible, since the curve and the pool balances are public, but the picture across multiple AMMs, aggregators, and intent-based execution venues is fragmented across many sources that have to be assembled into a coherent view. The aggregators doing the assembly are themselves running internal calculations on data they pull from each venue, with the result presented as a single number that the consumer reads on faith.
For an institutional desk evaluating execution quality, comparing realized slippage to expected slippage requires a baseline the desk can stand behind. The depth that was actually present at the moment of execution, the spreads available at competing venues, the price impact a comparable trade would have caused on each, all of that information lives in the chain state and the venue tapes, and reconstructing it accurately enough to support a best-execution finding is the work that desks pay analytics firms to do for them. The result is useful, and it is still a third party's interpretation of data the desk cannot independently verify.
Execution data with cryptographic proof attached
Verifiable liquidity and trading data treats the data itself as evidence rather than reporting. Onchain order book state, AMM curves and pool balances, executed trades, and the cross-venue context that surrounds them all live on the chain and in the contracts that produce them. Indexing that data and running the queries an institutional desk needs, depth at a price level, realized versus expected slippage, execution quality versus competing venues, produces results that come with a cryptographic proof of how each number was calculated and against what underlying state.
Space and Time runs that indexing and querying directly against the source. The institutional desk gets the depth, slippage, and execution-quality data its sizing and review processes require, with each result verifiable against the chain directly. The same evidence supports the routing decision before the trade, the execution analytics during it, and the best-execution review after.
The architecture preserves what aggregators and analytics providers do well, since the underlying data those tools rely on still lives in the same place. What changes is that the institutional desk gains a verifiable record it can build its own analysis on directly, alongside whatever third-party interpretations remain useful. The proof of liquidity and execution travels with the data itself.
Trading decisions an institutional desk can defend
For institutional traders, verifiable liquidity data turns sizing and routing into decisions a desk can defend against any review function that looks at them. Realized execution gets compared to expected execution against a baseline the desk produced from chain state directly, and the venues, aggregators, and intent networks competing for institutional flow can demonstrate the execution quality they offer with the same evidence the desks are using to evaluate them.
The structural advantage of having execution data anchored in chain state becomes the operational basis for how institutional capital evaluates its venues. Trading decisions get made against verifiable evidence, and the venues that produce the best evidence earn the flow that follows.
Liquidity and trading data is one of the areas covered by the CLARITY Compliance Framework by Space and Time, the data blockchain securing onchain finance.
