Hour audit: 2026-09-17T08
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-17T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T08:00:00.000238354+00:00 · last event 2026-09-17T08:59:59.999994035+00:00
VOLUME 104,583,570 rows · 1,052,558,240 bytes (1003.80 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 104,324,266 · h: 104,294,572 · e: 104,255,782 · f: 104,251,441 · g: 104,238,814 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 100,712,994 (96.30%) · h: 3,269,734 (3.13%) · e: 344,957 (0.33%) · f: 152,869 (0.15%) · g: 103,016 (0.10%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 104,583,570 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0945be80bff8a3ea78a01c5050999b93b2d014b6d598f92fc733fc773e1044b1
the corpus checksum ledger names this file with the same digest
joined 104,585,848 to merged 104,583,570, minus 2,278 (minus 0.0022%)
boundary drops 2,278 · 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-17T09:57:33Z 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: Perpetuals maintenance, on a market this archive does not record, 2026-09-17T08:00Z to 2026-09-17T08:32ZThe 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,529,378 128,243,392 0-43 53264bd55dc31e2dee341b952e83773bad4c76814b8e9bac60a3054136d813c1 book 418,484 41,668,940 44-45 214f2b29f0b9e9d14dfbc2ad21644a93b06c6e75cb5ed3c4c2ee714bb69d539a last_trade_price 47,609 2,694,435 46-46 ece85f432cc0053a52392318909af88df57bb42121b4d258e1e22696b2ffbad4 market_resolved 580 95,471 47-47 3b498c52bdba8c29edfac1040733e307a73c566ed2b1837b18cb88400fda0c2b new_market 735 77,928 48-48 232dd43fda36f6aed0f9639db2d21bc4eb844afcbd6733a8b195600939e289aa price_change 92,584,396 878,498,819 49-402 35cd7cc991454f97adc1988f485edfa4f6c795d54b81452f1f263a6c3effcf60 tick_size_change 2,388 87,648 403-403 161f6e737333c5c801e70dd265e2b802928ad7529c48b2717efb06402fd927ea EVENT MIX count share price_change 92,584,396 88.53% best_bid_ask 11,529,378 11.02% book 418,484 0.40% last_trade_price 47,609 0.05% tick_size_change 2,388 <0.01% new_market 735 <0.01% market_resolved 580 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,529,598 11,529,378 220 151 FULL book 418,814 418,484 330 118,359 FULL last_trade_price 47,611 47,609 2 2 FULL market_resolved 580 580 0 0 FULL new_market 735 735 0 0 FULL price_change 92,586,122 92,584,396 1,726 49 FULL tick_size_change 2,388 2,388 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,528,060 11,163,673 5ms 9ms 64ms 3.1s 0 transport_latency_assumed best_bid_ask e 11,526,079 27,959 37ms 42ms 116ms 4.4s 0 transport_latency_assumed best_bid_ask f 11,526,550 8,565 46ms 51ms 143ms 7.7s 0 transport_latency_assumed best_bid_ask g 11,525,540 909 76ms 92ms 227ms 13.3s 0 transport_latency_assumed best_bid_ask h 11,527,153 328,272 18ms 23ms 86ms 6.9s 0 transport_latency_assumed book c 186,107 167,395 34ms 23.7min 25.8d 110.4d 0 book_staleness book e 150,248 44,932 44ms 12.7min 18.7d 110.4d 0 book_staleness book f 156,660 49,217 57ms 15.7min 25.8d 110.4d 0 book_staleness book g 204,751 90,672 4.0s 28.7min 25.8d 110.4d 0 book_staleness book h 170,500 66,268 42ms 23.5min 25.8d 110.4d 0 book_staleness last_trade_price c 47,472 45,277 10ms 42ms 194ms 5.0s 0 transport_latency_assumed last_trade_price e 47,316 231 44ms 121ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price f 47,314 111 53ms 122ms 809ms 5.0s 0 transport_latency_assumed last_trade_price g 47,218 44 91ms 224ms 2.7s 7.6s 0 transport_latency_assumed last_trade_price h 47,320 1,946 24ms 70ms 241ms 5.0s 0 transport_latency_assumed market_resolved c 580 572 5ms 10ms 47ms 198ms 0 transport_latency_assumed market_resolved e 580 not meas. 112ms 199ms 374ms 506ms 0 transport_latency_assumed market_resolved f 580 not meas. 120ms 201ms 505ms 1.2s 0 transport_latency_assumed market_resolved g 580 not meas. 206ms 337ms 677ms 913ms 0 transport_latency_assumed market_resolved h 580 8 40ms 77ms 125ms 145ms 0 transport_latency_assumed new_market c 501 295 65ms 407ms 46.4s 55.5s 0 transport_latency_assumed new_market e 501 85 127ms 14.7s 23.6s 1.0min 0 transport_latency_assumed new_market f 501 76 165ms 18.3s 23.6s 1.2min 0 transport_latency_assumed new_market g 501 39 233ms 16.1s 24.5s 1.2min 0 transport_latency_assumed new_market h 501 240 101ms 16.6s 23.1s 1.3min 0 transport_latency_assumed price_change c 92,559,158 89,333,450 5ms 10ms 76ms 3.5s 0 transport_latency_assumed price_change e 92,528,670 271,750 37ms 44ms 185ms 4.4s 0 transport_latency_assumed price_change f 92,517,448 94,900 46ms 55ms 202ms 8.6s 0 transport_latency_assumed price_change g 92,457,836 11,352 76ms 95ms 343ms 14.2s 0 transport_latency_assumed price_change h 92,546,130 2,872,944 18ms 26ms 118ms 7.3s 0 transport_latency_assumed tick_size_change c 2,388 2,332 5ms 8ms 33ms 75ms 0 transport_latency_assumed tick_size_change e 2,388 not meas. 37ms 46ms 113ms 121ms 0 transport_latency_assumed tick_size_change f 2,388 not meas. 46ms 50ms 66ms 94ms 0 transport_latency_assumed tick_size_change g 2,388 not meas. 76ms 90ms 126ms 337ms 0 transport_latency_assumed tick_size_change h 2,388 56 18ms 22ms 47ms 1.4s 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-17/08/2026-09-17T08.parquet sha256sum 2026-09-17T08.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.