Hour audit: 2026-09-10T00
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-10T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T00:00:00.000010310+00:00 · last event 2026-09-10T00:59:59.999983880+00:00
VOLUME 125,711,975 rows · 1,348,374,318 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 124,210,207 · e: 124,188,630 · g: 120,051,279 · f: 119,388,711 · c: 108,120,114 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 19,385,020 (15.42%) · e: 1,915,364 (1.52%) · g: 224,198 (0.18%) · f: 456,701 (0.36%) · c: 103,730,692 (82.51%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 125,711,975 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e74406590d0d2b6ffdbfabcf202c5a8aa23955bb25c4d1a862930a4c8be77296
the corpus checksum ledger names this file with the same digest
joined 125,715,209 to merged 125,711,975, minus 3,234 (minus 0.0026%)
boundary drops 3,234 · 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-10T02:38:34Z 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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The 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 12,647,254 140,692,036 0-48 3e5dd3c73e8190b7c165a2b58bea96cc4c64e979198b53a47740fb86d81af4ab book 1,597,374 88,816,977 49-55 17c5775bab9a25a56a8d98679d5547cbf9c96d5f396c3e14a6275526a30b7cc6 last_trade_price 75,590 4,179,578 56-56 639046675cd80c71e09cb3d09f3131d43ee0b574f831d5d701329f508950fb06 market_resolved 727 98,396 57-57 354f3e9b0619ee7ca188f85166a0e1a09c8d47a9150142ba48a87a1e3504655a new_market 1,009 104,723 58-58 07643bb95acbc44b3aeabb98804808ec24f7d65fe3bc4101f8453c086a60df42 price_change 111,386,165 1,112,911,779 59-483 718593ff14b9599238202e54d071c078c6d1bd0eacb0d2190819d403a8fef3cf tick_size_change 3,856 139,792 484-484 5d1eec95e280c8ae9485122234672e6fc2edd9efe017eaa66ff48a93def45c0a EVENT MIX count share price_change 111,386,165 88.60% best_bid_ask 12,647,254 10.06% book 1,597,374 1.27% last_trade_price 75,590 0.06% tick_size_change 3,856 <0.01% new_market 1,009 <0.01% market_resolved 727 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,647,434 12,647,254 180 1,815 FULL book 1,597,382 1,597,374 8 197,100 FULL last_trade_price 75,592 75,590 2 353 FULL market_resolved 727 727 0 18 FULL new_market 1,009 1,009 0 0 FULL price_change 111,389,209 111,386,165 3,044 1,112 FULL tick_size_change 3,856 3,856 0 93 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,928,996 10,511,012 5ms 10ms 88ms 5.6s 0 transport_latency_assumed best_bid_ask e 12,644,518 186,245 40ms 50ms 166ms 5.7s 0 transport_latency_assumed best_bid_ask f 12,116,566 28,848 47ms 60ms 186ms 4.8s 0 transport_latency_assumed best_bid_ask g 12,196,269 4,274 83ms 101ms 277ms 13.5s 0 transport_latency_assumed best_bid_ask h 12,645,432 1,916,875 17ms 32ms 129ms 48.2s 0 transport_latency_assumed book c 1,380,559 1,239,745 11.4min 19.2h 29.2d 103.1d 0 book_staleness book e 183,539 13,240 45ms 1.6min 2.2d 84.6d 0 book_staleness book f 559,385 146,966 3.5min 15.5h 25.4d 103.1d 0 book_staleness book g 601,796 165,326 4.1min 15.6h 25.6d 103.1d 0 book_staleness book h 168,284 32,097 21ms 127ms 8.0h 84.6d 0 book_staleness last_trade_price c 63,312 59,762 10ms 45ms 255ms 5.0s 0 transport_latency_assumed last_trade_price e 75,227 1,344 50ms 194ms 2.4s 5.7s 0 transport_latency_assumed last_trade_price f 70,270 407 56ms 184ms 1.1s 5.1s 0 transport_latency_assumed last_trade_price g 72,810 303 94ms 190ms 2.4s 7.6s 0 transport_latency_assumed last_trade_price h 75,286 13,774 24ms 81ms 386ms 13.6s 0 transport_latency_assumed market_resolved c 603 542 5ms 4.6min 9.9min 10.3min 0 transport_latency_assumed market_resolved e 590 11 42ms 122ms 43.6s 51.3s 0 transport_latency_assumed market_resolved f 589 51 49ms 416ms 4.7min 4.7min 0 transport_latency_assumed market_resolved g 590 19 90ms 251ms 6.1min 6.1min 0 transport_latency_assumed market_resolved h 590 104 18ms 65ms 46.9s 1.0min 0 transport_latency_assumed new_market c 784 503 82ms 5.6min 6.3min 6.3min 0 transport_latency_assumed new_market e 662 127 107ms 14.2s 1.6min 1.9min 0 transport_latency_assumed new_market f 662 87 109ms 510ms 4.0min 4.0min 0 transport_latency_assumed new_market g 664 62 131ms 11.7s 1.7min 4.6min 0 transport_latency_assumed new_market h 662 230 68ms 821ms 1.6min 1.8min 0 transport_latency_assumed price_change c 95,742,212 91,915,625 5ms 12ms 97ms 5.6s 0 transport_latency_assumed price_change e 111,280,238 1,714,341 41ms 55ms 229ms 5.7s 0 transport_latency_assumed price_change f 106,637,455 280,338 47ms 65ms 242ms 4.9s 0 transport_latency_assumed price_change g 107,175,454 54,214 83ms 106ms 322ms 13.5s 0 transport_latency_assumed price_change h 111,316,097 17,421,647 17ms 35ms 146ms 48.5s 0 transport_latency_assumed tick_size_change c 3,648 3,503 5ms 10ms 45ms 105ms 0 transport_latency_assumed tick_size_change e 3,856 56 40ms 45ms 80ms 245ms 0 transport_latency_assumed tick_size_change f 3,784 4 47ms 53ms 88ms 157ms 0 transport_latency_assumed tick_size_change g 3,696 not meas. 80ms 95ms 137ms 301ms 0 transport_latency_assumed tick_size_change h 3,856 293 17ms 27ms 69ms 100ms 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-10/00/2026-09-10T00.parquet sha256sum 2026-09-10T00.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.