Hour audit: 2026-09-09T00
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-09T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T00:00:00.003020214+00:00 · last event 2026-09-09T00:59:59.999120282+00:00
VOLUME 101,800,404 rows · 1,008,602,762 bytes (961.88 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 101,727,862 · f: 101,709,827 · h: 101,639,953 · g: 101,634,504 · e: 101,541,261 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 98,082,764 (96.35%) · f: 137,985 (0.14%) · h: 3,207,874 (3.15%) · g: 47,561 (0.05%) · e: 324,220 (0.32%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,800,404 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f3d62b80f118f038856c69bcf9510304163258676c226294f88488a9a66b7f32
the corpus checksum ledger names this file with the same digest
joined 101,802,380 to merged 101,800,404, minus 1,976 (minus 0.0019%)
boundary drops 1,976 · guard cache
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 merged 2026-09-09T01:56:53Z as cefgh
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM an incident recorded by the venue intersects this hour: Perpetuals maintenance that overran, on a market this archive does not record, 2026-09-08T22:02Z to 2026-09-09T00:38ZThe 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 10,611,647 115,972,072 0-40 3637563eb3838b447c39c999c36c2b59dc06735189e9dc8904fa3efb02c0e7cb book 135,842 13,127,386 41-41 7dc86c258b37764bb6f80ff41cc911e6f1386a6cdad2672936fdce49c7520ba1 last_trade_price 54,047 3,071,592 42-42 ca3edeb61118e296c27f250ff69471d7dd3c449ba219418ede5dab1bf1a7b660 market_resolved 714 112,141 43-43 3613a2aae143ac5c62c5781a4ab72b78b8a97cefff9ef4a769534a8920a4fc27 new_market 1,771 176,783 44-44 257dd84f054a5d8d7f826eed0e68029efae362094dbbb96857ad8dd10fb835cf price_change 90,994,167 874,899,774 45-392 fd59160630c2219b38ebf6829b605b40a0bf9c44e95db7da1ada61ae068ef7cc tick_size_change 2,216 80,685 393-393 2479f5ff9f7565a2c149c2d1b36d85efebb2f5fcfeb64722d1b1c1f14a4a726e EVENT MIX count share price_change 90,994,167 89.38% best_bid_ask 10,611,647 10.42% book 135,842 0.13% last_trade_price 54,047 0.05% tick_size_change 2,216 <0.01% new_market 1,771 <0.01% market_resolved 714 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,611,781 10,611,647 134 268 FULL book 135,846 135,842 4 9,520 FULL last_trade_price 54,049 54,047 2 0 FULL market_resolved 714 714 0 0 FULL new_market 1,771 1,771 0 6 FULL price_change 90,996,003 90,994,167 1,836 390 FULL tick_size_change 2,216 2,216 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,610,764 10,245,376 5ms 8ms 97ms 4.3s 0 transport_latency_assumed best_bid_ask e 10,608,030 32,350 41ms 46ms 148ms 12.7s 0 transport_latency_assumed best_bid_ask f 10,609,349 13,699 46ms 53ms 165ms 7.9s 0 transport_latency_assumed best_bid_ask g 10,607,501 1,658 84ms 101ms 316ms 20.0s 0 transport_latency_assumed best_bid_ask h 10,610,200 318,564 17ms 21ms 135ms 17.6s 0 transport_latency_assumed book c 117,920 112,124 6ms 40ms 5.6h 84.0d 0 book_staleness book e 114,135 3,302 43ms 120ms 9.8min 83.5d 0 book_staleness book f 113,020 1,255 48ms 112ms 2.7s 83.6d 0 book_staleness book g 123,945 12,528 89ms 3.7s 1.1d 83.6d 0 book_staleness book h 114,491 6,633 20ms 53ms 4.9min 83.6d 0 book_staleness last_trade_price c 54,017 51,689 9ms 37ms 218ms 5.0s 0 transport_latency_assumed last_trade_price e 53,721 197 47ms 95ms 2.1s 12.8s 0 transport_latency_assumed last_trade_price f 54,023 102 52ms 103ms 977ms 7.9s 0 transport_latency_assumed last_trade_price g 53,756 12 95ms 185ms 3.4s 20.2s 0 transport_latency_assumed last_trade_price h 54,025 2,047 22ms 56ms 399ms 6.3s 0 transport_latency_assumed market_resolved c 683 646 5ms 12ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 683 47 42ms 273ms 54.9s 1.0min 0 transport_latency_assumed market_resolved f 683 4 47ms 275ms 55.5s 1.0min 0 transport_latency_assumed market_resolved g 683 5 87ms 373ms 58.7s 1.0min 0 transport_latency_assumed market_resolved h 683 12 18ms 127ms 58.4s 58.9s 0 transport_latency_assumed new_market c 1,146 731 80ms 29.7s 1.3min 1.4min 0 transport_latency_assumed new_market e 1,141 210 150ms 34.9s 1.3min 1.5min 0 transport_latency_assumed new_market f 1,146 193 144ms 33.3s 1.5min 1.6min 0 transport_latency_assumed new_market g 1,140 125 227ms 31.9s 1.2min 1.5min 0 transport_latency_assumed new_market h 1,146 512 104ms 34.0s 1.4min 1.5min 0 transport_latency_assumed price_change c 90,941,116 87,670,058 5ms 9ms 107ms 5.0s 0 transport_latency_assumed price_change e 90,761,335 288,114 41ms 48ms 186ms 12.8s 0 transport_latency_assumed price_change f 90,929,390 122,732 46ms 55ms 206ms 7.9s 0 transport_latency_assumed price_change g 90,845,263 33,233 84ms 104ms 367ms 20.3s 0 transport_latency_assumed price_change h 90,857,192 2,880,030 17ms 23ms 153ms 22.6s 0 transport_latency_assumed tick_size_change c 2,216 2,140 5ms 8ms 61ms 81ms 0 transport_latency_assumed tick_size_change e 2,216 not meas. 40ms 45ms 103ms 136ms 0 transport_latency_assumed tick_size_change f 2,216 not meas. 46ms 49ms 58ms 124ms 0 transport_latency_assumed tick_size_change g 2,216 not meas. 82ms 96ms 106ms 206ms 0 transport_latency_assumed tick_size_change h 2,216 76 17ms 19ms 34ms 42ms 0 transport_latency_assumed
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-09-09/00/2026-09-09T00.parquet sha256sum 2026-09-09T00.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.