Hour audit: 2026-09-19T18
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-19T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T18:00:00.005931553+00:00 · last event 2026-09-19T18:59:59.999983903+00:00
VOLUME 8,877,520 rows · 126,349,209 bytes (120.50 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 8,834,648 · g: 8,832,629 · e: 8,829,874 · f: 8,828,513 · h: 8,825,092 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 8,498,144 (95.73%) · g: 18,047 (0.20%) · e: 27,100 (0.31%) · f: 16,909 (0.19%) · h: 317,320 (3.57%) (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 8,877,520 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 23459a5a0a46248063a09c3842ee2f91c665899ec7698434a4fd19526c5d9754
the corpus checksum ledger names this file with the same digest
joined 8,877,776 to merged 8,877,520, minus 256 (minus 0.0029%)
boundary drops 256 · 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-19T19:37:31Z 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: Trading degraded, then cancel-only mode, 2026-09-19T16:54Z to 2026-09-19T18: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 1,166,826 23,417,200 0-4 5fd3d4ac753320618bb2bff66675521e1d63b1d9b750ac98bc5311f503d1cf3f book 73,119 6,535,863 5-5 b8f7ad1a8dc373bede4618cf8ceab44cddeba02ff45079b3aa71580f684861ec last_trade_price 8,080 555,443 6-6 bec79d44ca030e2e8c7d84bd17a988c440dcd404fadf70ab88f40dd3ddd3f550 market_resolved 3,659 583,166 7-7 bab102e59de4ef469196e65f57cf438d5a0636db3501b6c94c882738588ceecb new_market 2,242 228,334 8-8 e38117bada1bfdaa37cf35d5c2a1fb64f35d8379c42b9ee802bf26962cb9a6dc price_change 7,617,914 94,713,637 9-38 67164404f56e9986a934a5cd39f19bec9bae007c32bdaccc9d9c476b4f1db013 tick_size_change 5,680 196,612 39-39 ddb3f620c27d87a91e9d9cc99f45194a36b3a05dddd80b732c14869fd9a86560 EVENT MIX count share price_change 7,617,914 85.81% best_bid_ask 1,166,826 13.14% book 73,119 0.82% last_trade_price 8,080 0.09% tick_size_change 5,680 0.06% market_resolved 3,659 0.04% new_market 2,242 0.03% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 1,166,866 1,166,826 40 15 FULL book 73,131 73,119 12 26,505 FULL last_trade_price 8,080 8,080 0 2 FULL market_resolved 3,659 3,659 0 0 FULL new_market 2,242 2,242 0 0 FULL price_change 7,618,118 7,617,914 204 60 FULL tick_size_change 5,680 5,680 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 1,166,814 1,122,710 5ms 11ms 73ms 2.6s 0 transport_latency_assumed best_bid_ask e 1,166,567 1,481 40ms 47ms 163ms 4.9s 0 transport_latency_assumed best_bid_ask f 1,166,550 681 45ms 51ms 125ms 2.0s 0 transport_latency_assumed best_bid_ask g 1,166,368 59 78ms 91ms 197ms 3.6s 0 transport_latency_assumed best_bid_ask h 1,166,714 41,895 19ms 24ms 81ms 16.6s 0 transport_latency_assumed book c 31,954 28,256 107ms 1.8h 28.2d 112.8d 0 book_staleness book e 32,226 13,453 1.2s 1.8h 28.2d 94.3d 0 book_staleness book f 28,188 9,584 73ms 1.5h 17.0d 94.3d 0 book_staleness book g 35,909 16,647 2.9s 2.6h 28.2d 112.8d 0 book_staleness book h 22,572 5,179 25ms 17.4min 9.4d 94.3d 0 book_staleness last_trade_price c 8,077 7,476 6ms 18ms 226ms 502ms 0 transport_latency_assumed last_trade_price e 8,078 16 42ms 169ms 3.2s 4.9s 0 transport_latency_assumed last_trade_price f 8,078 22 47ms 98ms 1.2s 2.0s 0 transport_latency_assumed last_trade_price g 8,055 1 80ms 182ms 1.9s 3.6s 0 transport_latency_assumed last_trade_price h 8,079 565 20ms 33ms 163ms 547ms 0 transport_latency_assumed market_resolved c 3,641 3,524 5ms 8ms 326ms 51.5s 0 transport_latency_assumed market_resolved e 3,641 48 42ms 190ms 803ms 1.0min 0 transport_latency_assumed market_resolved f 3,641 9 48ms 197ms 586ms 1.0min 0 transport_latency_assumed market_resolved g 3,641 2 81ms 297ms 623ms 2.2min 0 transport_latency_assumed market_resolved h 3,641 76 20ms 61ms 477ms 1.0min 0 transport_latency_assumed new_market c 1,456 854 99ms 13.9s 57.4s 31.3min 0 transport_latency_assumed new_market e 1,456 360 138ms 17.7s 1.3min 45.4min 0 transport_latency_assumed new_market f 1,456 312 149ms 22.6s 1.4min 51.6min 0 transport_latency_assumed new_market g 1,456 173 219ms 15.8s 1.2min 55.3min 0 transport_latency_assumed new_market h 1,456 543 152ms 18.7s 1.2min 1.5h 0 transport_latency_assumed price_change c 7,617,026 7,329,720 5ms 12ms 108ms 4.5s 0 transport_latency_assumed price_change e 7,612,226 11,742 40ms 55ms 380ms 4.9s 0 transport_latency_assumed price_change f 7,614,920 6,301 46ms 54ms 214ms 2.0s 0 transport_latency_assumed price_change g 7,611,520 1,165 78ms 94ms 379ms 3.6s 0 transport_latency_assumed price_change h 7,616,950 268,986 19ms 27ms 129ms 16.6s 0 transport_latency_assumed tick_size_change c 5,680 5,604 5ms 9ms 23ms 61ms 0 transport_latency_assumed tick_size_change e 5,680 not meas. 39ms 43ms 65ms 112ms 0 transport_latency_assumed tick_size_change f 5,680 not meas. 45ms 49ms 60ms 76ms 0 transport_latency_assumed tick_size_change g 5,680 not meas. 78ms 89ms 100ms 197ms 0 transport_latency_assumed tick_size_change h 5,680 76 19ms 23ms 41ms 63ms 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-19/18/2026-09-19T18.parquet sha256sum 2026-09-19T18.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.