Hour audit: 2026-09-19T16
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-19T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T16:00:00.000004946+00:00 · last event 2026-09-19T16:59:59.999944176+00:00
VOLUME 140,933,886 rows · 1,613,545,933 bytes (1.50 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 130,849,410 · e: 119,072,240 · f: 111,472,840 · g: 108,379,181 · c: 98,361,862 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 35,629,341 (25.28%) · e: 8,056,198 (5.72%) · f: 3,318,085 (2.35%) · g: 1,037,854 (0.74%) · c: 92,892,408 (65.91%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 828a168ce55c3c423a2420a10269493c7fabc52f6171f370e504f791219d2574
the corpus checksum ledger names this file with the same digest
joined 140,984,053 to merged 140,933,886, minus 50,167 (minus 0.0356%)
boundary drops 50,167 · 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-19T18:07:41Z 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 15,245,380 177,242,486 0-58 5a56210bedd973cd69c7e9555bc72707c9c8e84399efd07ac9c1524e57a62b69 book 4,155,814 157,653,893 59-74 ab0812562f3cd6d9ff6e691c689d28bca1169e5cba09eff405e1698347c67294 last_trade_price 69,124 4,097,404 75-75 3bab0b3b51e648adf96c5bee56ad491571f5b320227eb9dcca35c75cd477a0f9 market_resolved 7,877 686,079 76-76 bca5a46cbc89238f64ae26324621c890b868b2c079f20877e959d36406ae4f81 new_market 2,307 162,708 77-77 d431ada2f986b50c6f20d81b64e4e0d966e0db63beab3af542facfdf165d6884 price_change 121,441,292 1,271,654,661 78-541 b40a7254ce86725ffcf8ee1e7bb495e128905f594a4716c0987f8e92fc947e77 tick_size_change 12,092 445,678 542-542 e4f040f2a52f5c99db951c1f4718151082a1c1a33aeea31a05917c68021ddf65 EVENT MIX count share price_change 121,441,292 86.17% best_bid_ask 15,245,380 10.82% book 4,155,814 2.95% last_trade_price 69,124 0.05% tick_size_change 12,092 <0.01% market_resolved 7,877 <0.01% new_market 2,307 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,245,517 15,245,380 137 10,113 FULL book 4,204,665 4,155,814 48,851 2,661 FULL last_trade_price 69,125 69,124 1 1,557 FULL market_resolved 7,899 7,877 22 580 FULL new_market 2,315 2,307 8 26 FULL price_change 121,442,440 121,441,292 1,148 4,482 FULL tick_size_change 12,092 12,092 0 1,796 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,485,024 9,977,469 5ms 14ms 136ms 5.1s 0 transport_latency_assumed best_bid_ask e 13,012,606 892,383 41ms 54ms 210ms 18.1s 0 transport_latency_assumed best_bid_ask f 12,080,925 327,439 48ms 62ms 231ms 16.6s 0 transport_latency_assumed best_bid_ask g 11,734,330 21,972 79ms 101ms 375ms 16.2s 0 transport_latency_assumed best_bid_ask h 14,473,963 4,026,117 19ms 49ms 170ms 50.8s 0 transport_latency_assumed book c 2,848,534 2,366,724 5.6min 1.0d 38.9d 112.8d 0 book_staleness book e 1,438,385 445,790 4.4min 1.0d 38.1d 112.8d 0 book_staleness book f 1,792,612 403,108 5.2min 1.0d 38.7d 112.8d 0 book_staleness book g 2,173,346 817,943 5.2min 1.0d 38.9d 112.8d 0 book_staleness book h 599,573 122,249 1.9min 17.2h 28.3d 112.8d 0 book_staleness last_trade_price c 49,901 47,146 10ms 48ms 381ms 5.0s 0 transport_latency_assumed last_trade_price e 59,743 2,691 50ms 153ms 1.9s 18.1s 0 transport_latency_assumed last_trade_price f 56,600 1,194 58ms 172ms 2.1s 15.7s 0 transport_latency_assumed last_trade_price g 55,055 175 93ms 341ms 4.5s 16.3s 0 transport_latency_assumed last_trade_price h 66,762 17,918 26ms 81ms 639ms 8.8s 0 transport_latency_assumed market_resolved c 5,412 3,416 46ms 18.3min 27.1min 27.6min 0 transport_latency_assumed market_resolved e 5,177 980 119ms 13.0min 18.1min 18.7min 0 transport_latency_assumed market_resolved f 3,925 598 120ms 6.5min 12.4min 14.1min 0 transport_latency_assumed market_resolved g 5,609 1,990 329ms 18.1min 26.2min 28.6min 0 transport_latency_assumed market_resolved h 3,897 893 38ms 160ms 8.4min 8.7min 0 transport_latency_assumed new_market c 1,745 1,209 19.9s 15.2min 28.3min 47.7min 0 transport_latency_assumed new_market e 1,144 282 226ms 6.1min 26.4min 45.1min 0 transport_latency_assumed new_market f 1,006 244 201ms 48.5s 17.6min 52.1min 0 transport_latency_assumed new_market g 1,469 214 523ms 16.5min 24.6min 44.0min 0 transport_latency_assumed new_market h 963 358 148ms 25.1s 7.5min 41.2min 0 transport_latency_assumed price_change c 84,964,614 80,490,026 5ms 16ms 192ms 8.9s 0 transport_latency_assumed price_change e 104,544,097 6,713,293 41ms 65ms 427ms 18.1s 0 transport_latency_assumed price_change f 97,528,148 2,585,458 49ms 73ms 471ms 16.7s 0 transport_latency_assumed price_change g 94,401,256 195,533 80ms 121ms 770ms 16.2s 0 transport_latency_assumed price_change h 115,692,432 31,456,982 19ms 53ms 251ms 50.9s 0 transport_latency_assumed tick_size_change c 6,632 6,418 5ms 10ms 44ms 454ms 0 transport_latency_assumed tick_size_change e 11,088 779 41ms 56ms 150ms 430ms 0 transport_latency_assumed tick_size_change f 9,624 44 48ms 54ms 101ms 290ms 0 transport_latency_assumed tick_size_change g 8,116 27 80ms 103ms 305ms 688ms 0 transport_latency_assumed tick_size_change h 11,820 4,824 19ms 47ms 99ms 472ms 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/16/2026-09-19T16.parquet sha256sum 2026-09-19T16.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.