Hour audit: 2026-09-19T20
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-19T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T20:00:00.004877271+00:00 · last event 2026-09-19T20:59:59.999972909+00:00
VOLUME 86,535,699 rows · 972,643,204 bytes (927.58 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 86,021,413 · f: 85,983,414 · e: 85,978,875 · c: 81,324,194 · g: 81,167,440 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 8,781,566 (10.15%) · f: 911,512 (1.05%) · e: 2,251,441 (2.60%) · c: 74,411,886 (85.99%) · g: 179,294 (0.21%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 cf7fdda876e4e9d77af2dd3d18279ee62568ec7a56b2769eb1def69998b51a9b
the corpus checksum ledger names this file with the same digest
joined 86,535,793 to merged 86,535,699, minus 94 (minus 0.0001%)
boundary drops 94 · 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-19T21:53:06Z 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 paused by degraded block production on Polygon, 2026-09-19T19:38Z to 2026-09-19T20:20ZThe 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,790,348 140,645,429 0-44 56c70294788b3df6c6b9b928c1373653e02ac7160b8e516144dcea830b58f77f book 613,863 53,529,878 45-47 f3ce76c4c53b275b22ee4c2c5c75ff55afa5dac7237918dd104071a93a3d0550 last_trade_price 50,252 3,003,229 48-48 96204a4f93fc90a7b11d584b84c34c65fb53ae98953c552d5e9a4e5d7235aa42 market_resolved 3,892 614,185 49-49 260aa19345de1d3f585c754cb4143b42519573f20d35d1d9bfa2eea565c3da51 new_market 9,393 903,042 50-50 4d6ee18aec0a1f5dc7f4ecea805c1a9fec60fb9653890e5c4645e56960edaf6f price_change 74,055,939 772,521,397 51-333 dcfc82f59efcef7d4e1c4a98437a0e3d93bc61ff6b4d3a893381919eb9fc22c0 tick_size_change 12,012 437,433 334-334 73d5500139118701d7ada3ff413f7b346e3f0d9f74708bb1caddab8967a5e7bb EVENT MIX count share price_change 74,055,939 85.58% best_bid_ask 11,790,348 13.62% book 613,863 0.71% last_trade_price 50,252 0.06% tick_size_change 12,012 0.01% new_market 9,393 0.01% market_resolved 3,892 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,790,352 11,790,348 4 1,264 FULL book 613,891 613,863 28 189,201 FULL last_trade_price 50,252 50,252 0 149 FULL market_resolved 3,894 3,892 2 124 FULL new_market 9,397 9,393 4 132 FULL price_change 74,055,995 74,055,939 56 762 FULL tick_size_change 12,012 12,012 0 200 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,150,748 10,255,021 5ms 27ms 389ms 9.1s 0 transport_latency_assumed best_bid_ask e 11,787,514 298,038 40ms 85ms 450ms 18.4s 0 transport_latency_assumed best_bid_ask f 11,787,605 118,984 46ms 105ms 498ms 19.3s 0 transport_latency_assumed best_bid_ask g 11,155,277 11,794 79ms 229ms 1.2s 45.7s 0 transport_latency_assumed best_bid_ask h 11,788,653 1,106,511 18ms 66ms 3.0s 1.6min 0 transport_latency_assumed book c 507,575 472,653 2.2min 17.8h 35.3d 112.9d 0 book_staleness book e 128,328 17,867 45ms 1.4min 8.1d 94.4d 0 book_staleness book f 125,937 13,388 51ms 39.5s 1.2d 94.4d 0 book_staleness book g 508,213 87,619 2.3min 17.5h 35.3d 112.9d 0 book_staleness book h 124,807 22,336 24ms 13.2s 1.2d 112.9d 0 book_staleness last_trade_price c 47,636 43,823 6ms 45ms 470ms 4.4s 0 transport_latency_assumed last_trade_price e 49,839 966 42ms 264ms 5.2s 18.4s 0 transport_latency_assumed last_trade_price f 49,883 375 48ms 335ms 5.9s 19.2s 0 transport_latency_assumed last_trade_price g 46,334 70 83ms 545ms 15.1s 45.1s 0 transport_latency_assumed last_trade_price h 50,172 5,018 19ms 133ms 2.7s 1.5min 0 transport_latency_assumed market_resolved c 3,656 3,414 5ms 101ms 5.0min 5.5min 0 transport_latency_assumed market_resolved e 3,714 77 43ms 201ms 666ms 33.5s 0 transport_latency_assumed market_resolved f 3,714 37 48ms 208ms 665ms 33.9s 0 transport_latency_assumed market_resolved g 3,593 19 83ms 395ms 4.8min 5.0min 0 transport_latency_assumed market_resolved h 3,713 345 20ms 92ms 1.0s 45.9s 0 transport_latency_assumed new_market c 5,573 3,132 160ms 3.7min 11.1min 2.3h 0 transport_latency_assumed new_market e 5,548 1,966 200ms 2.4min 7.1min 1.0h 0 transport_latency_assumed new_market f 5,562 1,395 224ms 2.5min 7.2min 2.3h 0 transport_latency_assumed new_market g 5,444 704 321ms 3.3min 10.2min 1.3h 0 transport_latency_assumed new_market h 5,562 2,196 208ms 2.6min 7.0min 12.3min 0 transport_latency_assumed price_change c 69,597,626 63,623,379 5ms 36ms 416ms 12.3s 0 transport_latency_assumed price_change e 73,991,920 1,932,250 40ms 116ms 563ms 18.5s 0 transport_latency_assumed price_change f 73,998,701 777,224 46ms 138ms 634ms 19.3s 0 transport_latency_assumed price_change g 69,436,915 79,072 79ms 297ms 2.6s 45.8s 0 transport_latency_assumed price_change h 74,036,502 7,644,014 18ms 87ms 3.2s 1.6min 0 transport_latency_assumed tick_size_change c 11,380 10,464 5ms 23ms 259ms 1.3s 0 transport_latency_assumed tick_size_change e 12,012 277 40ms 71ms 423ms 714ms 0 transport_latency_assumed tick_size_change f 12,012 109 46ms 88ms 427ms 737ms 0 transport_latency_assumed tick_size_change g 11,664 16 78ms 180ms 772ms 2.2s 0 transport_latency_assumed tick_size_change h 12,004 1,146 18ms 45ms 741ms 33.9s 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/20/2026-09-19T20.parquet sha256sum 2026-09-19T20.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.