Hour audit: 2026-08-19T11
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-19T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-19T11:00:00.000814+00:00 · last event 2026-08-19T11:59:59.999986+00:00
VOLUME 39,165,622 rows · 331,947,801 bytes (316.57 MiB) · 7 products, all holding rows
WITNESSES not measured (this hour carries no per-machine row accounting)
INTEGRITY sha256 9c76b2413f66cb3e98f38210995c0379d0abf3b091bb87e502b5f348d9d4ce1d
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: Trading outage, order submissions failing, 2026-08-19T09:19Z to 2026-08-19T10:58ZThe 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 3,333,964 32,541,093 0-12 d82e1a3d6227db21887b55d6a91e209a82ace33b04dfb8ddecd8962b4a4c7f5a book 152,158 13,585,878 13-13 79f5ffca5778049e3aa09630d9b8c56fbd458994bb43110548a2a214afe71e1a last_trade_price 59,259 3,206,169 14-14 2f7c19152ced7a7e02ee21e651fdda8bc947a58f9b67c8ec08c2f06a63e21d44 market_resolved 985 152,920 15-15 f798c1be228510ea66601fdb6460b59b21670fc62fdb5a8184b329efebe62594 new_market 984 111,488 16-16 aec527b0264c4d90a9197ded027917543d6982cc53fa4fcfa4c020d250e8c659 price_change 35,614,636 281,823,815 17-152 b605befb5c18f93503d42074e6c6dc9243e9fbabc2804cf3f017d3d141975185 tick_size_change 3,636 123,421 153-153 47c1658353fa13f619455e6dbf42ddb78c6611a8d71b55aa17dedbd4b034c3aa EVENT MIX count share price_change 35,614,636 90.93% best_bid_ask 3,333,964 8.51% book 152,158 0.39% last_trade_price 59,259 0.15% tick_size_change 3,636 <0.01% market_resolved 985 <0.01% new_market 984 <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-19/11/2026-08-19T11.parquet sha256sum 2026-08-19T11.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.