Hour audit: 2026-09-20T18
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-20T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T18:00:00.000007483+00:00 · last event 2026-09-20T18:59:59.999984196+00:00
VOLUME 148,267,501 rows · 1,702,905,915 bytes (1.59 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 144,430,461 · e: 138,746,579 · g: 118,968,411 · f: 108,315,688 · c: 96,259,455 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 51,695,347 (34.87%) · e: 3,662,472 (2.47%) · g: 479,436 (0.32%) · f: 2,016,805 (1.36%) · c: 90,413,441 (60.98%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 9d400a4bb84d069de50784de1f32e75aa6e2d43dd4773cf063ff215df42131f4
the corpus checksum ledger names this file with the same digest
joined 148,289,416 to merged 148,267,501, minus 21,915 (minus 0.0148%)
boundary drops 21,915 · 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-20T21:17:40Z 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 14,387,611 170,546,585 0-54 00897e82174018885947514ddc9e06af361807d7c195f92d25a8cf354957dc82 book 3,960,615 136,557,274 55-70 0aa1e5c51ddaa6657e318fcb0c95d39d64be2ef8c2b7278c0974282c2631fe26 last_trade_price 64,137 3,759,494 71-71 f68f1127f264e90f01a7681cc89dc4d2691fe705012cf50c3658bf5bec8f7556 market_resolved 12,789 1,220,810 72-72 010056d0dcf28324c2a1c5dc300cec2a7f50691ec953ddf9fafee4cfb551da98 new_market 12,071 666,909 73-73 789e07334cae7631d6a652769ec718b68fcfe94d2b9c1f542287eac27330c82a price_change 129,819,838 1,388,082,775 74-569 f29978a03553f7f08e53e4ed474d202af589d522eff27220c24e939857943b43 tick_size_change 10,440 385,744 570-570 7652163f8430e8b6fb6ed3c4ee196bf12478d9ccb818cdb5cd3363d9594e6757 EVENT MIX count share price_change 129,819,838 87.56% best_bid_ask 14,387,611 9.70% book 3,960,615 2.67% last_trade_price 64,137 0.04% market_resolved 12,789 <0.01% new_market 12,071 <0.01% tick_size_change 10,440 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,387,909 14,387,611 298 10,417 FULL book 3,979,044 3,960,615 18,429 150,130 FULL last_trade_price 64,138 64,137 1 1,332 FULL market_resolved 12,789 12,789 0 4,422 FULL new_market 12,076 12,071 5 2,498 FULL price_change 129,823,020 129,819,838 3,182 5,997 FULL tick_size_change 10,440 10,440 0 1,413 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,423,501 8,898,890 6ms 17ms 114ms 6.8s 0 transport_latency_assumed best_bid_ask e 13,845,134 323,267 46ms 66ms 280ms 24.7s 0 transport_latency_assumed best_bid_ask f 10,639,030 113,856 46ms 68ms 286ms 25.8s 0 transport_latency_assumed best_bid_ask g 11,726,109 10,752 79ms 129ms 762ms 30.2s 0 transport_latency_assumed best_bid_ask h 14,385,086 5,040,846 19ms 45ms 194ms 45.8s 0 transport_latency_assumed book c 3,030,908 2,612,493 7.1min 2.1d 43.2d 113.9d 0 book_staleness book e 525,425 162,513 1.5min 1.8d 39.7d 113.8d 0 book_staleness book f 2,294,252 782,640 6.5min 2.1d 43.2d 113.9d 0 book_staleness book g 1,246,490 343,069 5.0min 2.1d 42.9d 113.9d 0 book_staleness book h 163,882 59,900 30ms 9.9min 13.3d 113.8d 0 book_staleness last_trade_price c 41,006 38,311 7ms 26ms 177ms 1.6s 0 transport_latency_assumed last_trade_price e 60,974 1,696 49ms 297ms 4.3s 24.7s 0 transport_latency_assumed last_trade_price f 46,950 558 50ms 430ms 5.7s 25.8s 0 transport_latency_assumed last_trade_price g 52,159 175 89ms 654ms 8.3s 30.2s 0 transport_latency_assumed last_trade_price h 64,059 23,397 21ms 73ms 513ms 8.8s 0 transport_latency_assumed market_resolved c 10,681 10,074 13.6min 55.0min 1.2h 1.2h 0 transport_latency_assumed market_resolved e 3,876 214 52ms 198ms 4.7min 5.0min 0 transport_latency_assumed market_resolved f 4,000 655 116ms 11.7min 16.4min 16.7min 0 transport_latency_assumed market_resolved g 4,541 585 199ms 8.6min 15.9min 16.4min 0 transport_latency_assumed market_resolved h 3,834 1,261 32ms 72ms 17.3s 1.0min 0 transport_latency_assumed new_market c 11,330 10,327 21.7min 54.7min 3.2h 19.4h 0 transport_latency_assumed new_market e 1,650 374 210ms 36.6s 1.5min 13.1h 0 transport_latency_assumed new_market f 1,975 332 356ms 13.1min 2.6h 21.8h 0 transport_latency_assumed new_market g 1,687 303 345ms 38.7s 40.3min 13.2h 0 transport_latency_assumed new_market h 1,642 735 112ms 30.2s 1.3min 1.5min 0 transport_latency_assumed price_change c 83,734,645 78,836,201 6ms 19ms 128ms 7.0s 0 transport_latency_assumed price_change e 124,299,332 3,174,148 46ms 78ms 543ms 25.1s 0 transport_latency_assumed price_change f 95,321,809 1,118,715 46ms 81ms 755ms 26.2s 0 transport_latency_assumed price_change g 105,928,909 124,546 80ms 163ms 2.3s 32.0s 0 transport_latency_assumed price_change h 129,801,518 46,566,228 19ms 50ms 237ms 48.2s 0 transport_latency_assumed tick_size_change c 7,384 7,145 6ms 12ms 87ms 421ms 0 transport_latency_assumed tick_size_change e 10,188 260 46ms 58ms 242ms 1.4s 0 transport_latency_assumed tick_size_change f 7,672 49 45ms 57ms 311ms 3.8s 0 transport_latency_assumed tick_size_change g 8,516 6 79ms 112ms 895ms 19.4s 0 transport_latency_assumed tick_size_change h 10,440 2,980 19ms 43ms 231ms 1.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-20/18/2026-09-20T18.parquet sha256sum 2026-09-20T18.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.