Hour audit: 2026-08-24T15
back to the files for this hour · how the archive is audited
Every number on this page is a stored measurement read from this hour's own records: its
manifest.json, its witness
statistics sidecar, and the corpus attestation. Nothing here is computed from the served
bytes at the time you load the page, so no line below claims the bytes are correct. The
digest and the one command that checks them are printed instead.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
3 checks could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-24T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-24T15:00:00.000486739+00:00 · last event 2026-08-24T15:59:59.999973659+00:00
VOLUME 103,743,456 rows · 916,056,626 bytes (873.62 MiB) · 7 products, all holding rows
WITNESSES not measured (this hour carries no per-machine row accounting)
INTEGRITY sha256 360c886b3940a52d549400102f921135047e6024b431a39a57e35b91c0030279
the corpus checksum ledger names this file with the same digest
SIDECARS none: this hour's manifest has no v31 key. The v3.1 sidecars are optional, and hours before them have none
MARKETS not measured (the per-hour market census runs on the capture host and its output is not published per hour)
HISTORY layout union-event-sorted-v1
re-merges not measured (the merge ledger records the merge that produced this file, not the history of attempts)
supersessions not measured (supersession is recorded per corpus in the storage registry, not in the hour manifest)
CHECKS 5/8 pass, 3 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
SKIPPED the merge delta could not be checked
SKIPPED which machines were expected is not published beside this hour
PASS the checksum ledger names this file
PASS the hour is whole
SKIPPED whether a boundary guard ran is not recorded
UPSTREAM an incident recorded by the venue intersects this hour: A day of trouble on a market this archive does not record, 2026-08-24T08:40Z to 2026-08-24T21:50ZThe words in this report
Each line in the CHECKS block states what was found, not what was
hoped for: a check that passes is named for the thing that is true, and a check that does
not is renamed to the thing that is wrong. So FINDING never sits beside a
sentence asserting the opposite of the one below it.
The report above is fixed-width text, so nothing in it can be clicked. The same terms are linked here instead. Its verdict is a statement about minutes and nothing else. The row it reports comes from this hour's own manifest and its witness-statistics sidecar, and the completeness line comes from the corpus attestation. The gap between the joined and merged counts is deduplication, not loss, and the boundary drops are the duplicates discarded at the seam with the hour before. Where the history line names a supersession, this hour was rebuilt to a better state after it was first published. The precision is the timestamp resolution these files carry.
Detail
The same records, per product. A product holding no rows renders its zero rather than
being dropped: dropped and empty are indistinguishable to a reader, and only one of them is
a defect. A cell reading not meas. is one nothing published, which is a third
thing again and never a zero.
The class column is the merger's own verdict for that product, and it is
keyed to CONTRIBUTION rather than presence. FULL means every machine expected to
be capturing this hour delivered rows for that product; PARTIAL means some did
and some did not; SINGLE-BY-DESIGN means only one machine was ever expected, and
SINGLE-BY-DEFECT means several were and one delivered. So PARTIAL
here is a statement about the fleet, not about the product being damaged or truncated: the
rows that are present are whole.
PRODUCT rows bytes row groups sha256 best_bid_ask 9,488,592 82,609,830 0-36 e84ed190c31cb11e385958e29ca957615cc609653d8180c4f2372499ada270a3 book 1,460,349 83,540,797 37-42 9b091f4f6eb217ca4e5812442e3d85bc41769e4860fe99f689ac6210b90bbc0a last_trade_price 96,390 4,878,962 43-43 317ee32c91b4d6a90c05cd71147d0aa9bfac438bf3f9733f7ea0d3273dbd081e market_resolved 786 101,467 44-44 e88a6b467c236dd6b1be4dd7738fdf92e8e3e634ea2b1f9e7141a5a94c6a7ff5 new_market 5,183 422,669 45-45 8a23ca4d50a3c56d46972ea3726c0954a1b6b3b71dee5404c8fc04fa2a7aea55 price_change 92,688,968 743,344,950 46-399 5d7c3a991aed6b7d4a8355791ac5d2cf000c017dc0efc2ac3dde7529aa9c10ba tick_size_change 3,188 108,617 400-400 46cc791a58dc08559d2e9596a8cf21396093f6460aeba460ab355dcffa48d0d9 EVENT MIX count share price_change 92,688,968 89.34% best_bid_ask 9,488,592 9.15% book 1,460,349 1.41% last_trade_price 96,390 0.09% new_market 5,183 <0.01% tick_size_change 3,188 <0.01% market_resolved 786 <0.01%
Captured and supplied are different numbers
Captured is how many rows each machine's own feed carried. Redundant capture means these OVERLAP, heavily and on purpose, so they do not partition the file and their sum is larger than it. Two machines each capturing nearly every event is the archive working, not double counting.
Supplied is how many rows of the merged file actually came from that machine. This one does partition: it sums to the file's row count exactly. But it is decided by the merge's tie-break, so a machine can capture almost everything and supply almost nothing. Read alone, either number tells a false story about the fleet, which is why both are printed and neither is called "the witness share".
What the skew columns mean
Arrival skew is the receipt timestamp minus the venue timestamp, in milliseconds. For six of the seven products the sidecar interprets it as transport latency, and marks that interpretation assumed: it rests on the venue timestamp being emit time, which we cannot verify from outside.
book is not latency and must not be read as latency. Its
venue timestamp is the last time the book changed, so the sidecar interprets it as book
staleness and warns in its own note that large values mean a quiet book rather than slow
transport. Its maximum runs to weeks for that reason. This is why the table above gives a
row per product per machine and never one figure for the hour: percentiles do not average,
and these seven do not measure the same quantity.
Check it yourself
The digest above is a claim. This is how you refuse to take our word for it:
curl -O https://archive.pendulumflow.com/v3/2026-08-24/15/2026-08-24T15.parquet sha256sum 2026-08-24T15.parquet # compare with the sha256 line in the report above
A range digest certifies bytes. That those bytes are the product the manifest names comes from the manifest, which is why both are published and both are checkable.