Hour audit: 2026-09-18T18
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-18T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T18:00:00.000119617+00:00 · last event 2026-09-18T18:59:59.999862622+00:00
VOLUME 114,011,378 rows · 1,303,447,554 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 111,192,728 · e: 110,393,641 · g: 109,386,094 · f: 101,126,951 · c: 82,486,879 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 32,343,923 (28.37%) · e: 4,207,763 (3.69%) · g: 275,241 (0.24%) · f: 1,852,961 (1.63%) · c: 75,331,490 (66.07%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 05096e0952bfc05930827eb7deda179100b4b2a3d18905e7c427fbbc5cff820a
the corpus checksum ledger names this file with the same digest
joined 114,015,487 to merged 114,011,378, minus 4,109 (minus 0.0036%)
boundary drops 4,109 · 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-18T21:41:51Z 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 11,708,297 142,511,021 0-44 2284c87f934a09bac1f14ec61c3a13030843cb576cd96a02a14516d84903e27b book 2,753,478 102,137,958 45-55 0150ece5417cfb8a0958b6e21dacb222d04b861ece8ab480432ffb934ebb8b60 last_trade_price 68,307 3,984,200 56-56 50bcda6276b1b3fe6fab153e36cb95818228223077ede3736fc88f13d57a3716 market_resolved 2,468 200,764 57-57 89c3dfeef2e585f5b5c70d7504746b181a976c12b15e7f8f8335611c1f5be1a4 new_market 24,850 1,400,761 58-58 625c4735f543a4c78dc2fc1aac3a571121a21d0220299ac8ee2900eb08edeb01 price_change 99,446,570 1,051,642,139 59-438 3d0946303d5bce1e98d5cfbd259faa07f8ae01f78d3014fa6a84a7d5eb5a40eb tick_size_change 7,408 272,603 439-439 82c5dcabc2ea4ac0c69ab1e55c0a4d3df17c707016e9c8bdbc019fbaa23807cf EVENT MIX count share price_change 99,446,570 87.23% best_bid_ask 11,708,297 10.27% book 2,753,478 2.42% last_trade_price 68,307 0.06% new_market 24,850 0.02% tick_size_change 7,408 <0.01% market_resolved 2,468 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,708,485 11,708,297 188 6,694 FULL book 2,756,001 2,753,478 2,523 204,686 FULL last_trade_price 68,307 68,307 0 812 FULL market_resolved 2,468 2,468 0 33 FULL new_market 24,852 24,850 2 19 FULL price_change 99,447,966 99,446,570 1,396 4,505 FULL tick_size_change 7,408 7,408 0 557 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,028,127 7,286,679 6ms 34ms 298ms 11.7s 0 transport_latency_assumed best_bid_ask e 11,691,332 509,089 43ms 126ms 441ms 26.4s 0 transport_latency_assumed best_bid_ask f 10,478,501 195,127 48ms 132ms 482ms 22.1s 0 transport_latency_assumed best_bid_ask g 11,680,805 26,511 85ms 303ms 1.2s 43.6s 0 transport_latency_assumed best_bid_ask h 11,699,924 3,690,891 19ms 81ms 880ms 40.7s 0 transport_latency_assumed book c 2,567,359 2,504,519 14.5min 3.1h 37.7d 111.8d 0 book_staleness book e 163,730 15,018 107ms 7.6s 3.0h 93.3d 0 book_staleness book f 992,153 174,929 9.0min 2.8h 34.2d 111.8d 0 book_staleness book g 167,286 14,298 225ms 58.3s 3.0d 93.3d 0 book_staleness book h 162,994 44,714 36ms 2.0s 2.6h 93.3d 0 book_staleness last_trade_price c 51,884 47,442 12ms 85ms 681ms 5.0s 0 transport_latency_assumed last_trade_price e 64,860 1,723 93ms 1.3s 11.5s 26.4s 0 transport_latency_assumed last_trade_price f 59,775 914 97ms 1.1s 11.8s 22.1s 0 transport_latency_assumed last_trade_price g 63,196 324 182ms 2.9s 23.8s 43.7s 0 transport_latency_assumed last_trade_price h 67,648 17,904 32ms 219ms 1.7s 40.6s 0 transport_latency_assumed market_resolved c 2,109 2,033 7.0min 24.2min 30.7min 31.5min 0 transport_latency_assumed market_resolved e 1,144 38 45ms 304ms 58.2s 1.0min 0 transport_latency_assumed market_resolved f 1,243 37 60ms 4.7min 12.4min 13.5min 0 transport_latency_assumed market_resolved g 1,144 4 90ms 501ms 1.3s 5.6s 0 transport_latency_assumed market_resolved h 1,144 356 23ms 168ms 54.8s 57.8s 0 transport_latency_assumed new_market c 22,875 17,904 16.4min 33.2min 40.9min 42.0min 0 transport_latency_assumed new_market e 7,741 1,744 169ms 10.4min 24.6min 29.1min 0 transport_latency_assumed new_market f 9,595 1,348 235ms 17.1min 24.9min 29.2min 0 transport_latency_assumed new_market g 7,741 958 277ms 9.4min 24.0min 29.3min 0 transport_latency_assumed new_market h 7,739 2,896 131ms 9.9min 24.0min 28.9min 0 transport_latency_assumed price_change c 71,809,173 65,468,016 6ms 35ms 319ms 12.2s 0 transport_latency_assumed price_change e 98,457,426 3,679,907 43ms 202ms 5.1s 26.6s 0 transport_latency_assumed price_change f 89,578,672 1,480,514 48ms 209ms 4.9s 22.2s 0 transport_latency_assumed price_change g 97,458,514 233,140 87ms 476ms 12.3s 43.7s 0 transport_latency_assumed price_change h 99,245,871 28,584,993 20ms 96ms 911ms 42.8s 0 transport_latency_assumed tick_size_change c 5,352 4,897 6ms 34ms 220ms 909ms 0 transport_latency_assumed tick_size_change e 7,408 244 42ms 89ms 371ms 2.5s 0 transport_latency_assumed tick_size_change f 7,012 92 47ms 88ms 389ms 2.5s 0 transport_latency_assumed tick_size_change g 7,408 6 82ms 219ms 685ms 16.2s 0 transport_latency_assumed tick_size_change h 7,408 2,169 19ms 51ms 370ms 2.8s 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-18/18/2026-09-18T18.parquet sha256sum 2026-09-18T18.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.