Hour audit: 2026-09-11T17
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-11T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T17:00:00.000016788+00:00 · last event 2026-09-11T17:59:59.999917839+00:00
VOLUME 93,268,067 rows · 983,778,750 bytes (938.20 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 93,079,641 · c: 92,883,962 · e: 92,870,011 · h: 92,869,075 · f: 92,855,664 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 309,119 (0.33%) · c: 88,872,413 (95.29%) · e: 460,451 (0.49%) · h: 3,408,167 (3.65%) · f: 217,917 (0.23%) (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 93,268,067 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0ee61f55a4516c98f259d683c2d62ca949d271cb76e8ba21ef7a25b1ce651413
the corpus checksum ledger names this file with the same digest
joined 93,271,887 to merged 93,268,067, minus 3,820 (minus 0.0041%)
boundary drops 3,820 · 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-11T18:55:26Z 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 for forty-one minutes, 2026-09-11T16:22Z to 2026-09-11T17:02ZThe 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 10,236,316 115,962,082 0-39 30d64b818b3ef1c4346e296c1d61156434be7b56002290b361687656b947bf67 book 526,077 48,265,610 40-42 be443dc863f6cfc60a05f7247a8ab8dbe84a4a10dc7091a2f0f58f3b1ef1c8b6 last_trade_price 54,042 3,102,693 43-43 6f7bcf80392c4f422932c5b3dab82b6720c0024edfeef64a85dbf476a1c412f4 market_resolved 946 150,595 44-44 22214d2e44623b7f138c6013c31752e6dfc9040dcd7153c085092482f4ef64d2 new_market 1,048 108,576 45-45 feba756149d2e21381d4e2ef094663eb5ba47e7d651dd1b45d4f661529bea5a5 price_change 82,445,934 814,986,867 46-360 caa050ea0426f0dc75b0039174d950f0766ae1e6a034ed63303becde3865061c tick_size_change 3,704 134,484 361-361 7eb99f2ab87b23d8be74f5c2ddcb0bea1b5801a8926e6d2751dd3aa3f7d144ef EVENT MIX count share price_change 82,445,934 88.40% best_bid_ask 10,236,316 10.98% book 526,077 0.56% last_trade_price 54,042 0.06% tick_size_change 3,704 <0.01% new_market 1,048 <0.01% market_resolved 946 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,236,755 10,236,316 439 134 FULL book 526,086 526,077 9 146,864 FULL last_trade_price 54,048 54,042 6 1 FULL market_resolved 946 946 0 0 FULL new_market 1,048 1,048 0 0 FULL price_change 82,449,300 82,445,934 3,366 86 FULL tick_size_change 3,704 3,704 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,235,393 9,825,330 5ms 11ms 124ms 6.5s 0 transport_latency_assumed best_bid_ask e 10,234,579 45,039 40ms 47ms 177ms 5.6s 0 transport_latency_assumed best_bid_ask f 10,234,340 17,068 44ms 53ms 209ms 7.5s 0 transport_latency_assumed best_bid_ask g 10,230,877 2,284 79ms 102ms 346ms 13.7s 0 transport_latency_assumed best_bid_ask h 10,234,971 346,595 18ms 28ms 153ms 37.6s 0 transport_latency_assumed book c 159,083 143,975 9ms 18.4min 6.2d 97.1d 0 book_staleness book e 153,564 33,782 46ms 21.2min 6.1d 104.8d 0 book_staleness book f 143,813 27,472 49ms 13.9min 4.3d 86.3d 0 book_staleness book g 409,399 282,948 2.9min 46.2min 20.2d 104.8d 0 book_staleness book h 154,405 37,900 25ms 21.5min 6.1d 86.3d 0 book_staleness last_trade_price c 53,908 51,364 11ms 44ms 228ms 5.0s 0 transport_latency_assumed last_trade_price e 53,966 326 49ms 148ms 893ms 5.6s 0 transport_latency_assumed last_trade_price f 53,877 186 55ms 177ms 1.5s 7.5s 0 transport_latency_assumed last_trade_price g 53,891 56 95ms 276ms 1.4s 5.8s 0 transport_latency_assumed last_trade_price h 53,915 2,110 24ms 78ms 430ms 5.0s 0 transport_latency_assumed market_resolved c 945 928 5ms 9ms 45ms 94ms 0 transport_latency_assumed market_resolved e 945 not meas. 40ms 118ms 313ms 513ms 0 transport_latency_assumed market_resolved f 945 not meas. 45ms 122ms 362ms 562ms 0 transport_latency_assumed market_resolved g 945 1 84ms 238ms 539ms 1.4min 0 transport_latency_assumed market_resolved h 945 17 18ms 54ms 121ms 7.9s 0 transport_latency_assumed new_market c 693 357 92ms 15.5s 1.2min 1.6min 0 transport_latency_assumed new_market e 693 144 179ms 22.1s 26.6s 1.0min 0 transport_latency_assumed new_market f 693 141 153ms 14.5s 1.2min 2.5min 0 transport_latency_assumed new_market g 693 88 263ms 18.1s 29.9s 1.3min 0 transport_latency_assumed new_market h 693 318 92ms 15.0s 24.9s 45.4s 0 transport_latency_assumed price_change c 82,430,236 78,846,960 5ms 12ms 157ms 6.6s 0 transport_latency_assumed price_change e 82,422,560 381,144 40ms 53ms 283ms 5.6s 0 transport_latency_assumed price_change f 82,418,292 173,042 45ms 61ms 355ms 7.5s 0 transport_latency_assumed price_change g 82,380,140 23,742 80ms 119ms 526ms 14.1s 0 transport_latency_assumed price_change h 82,420,442 3,021,046 18ms 33ms 206ms 39.5s 0 transport_latency_assumed tick_size_change c 3,704 3,499 5ms 12ms 390ms 851ms 0 transport_latency_assumed tick_size_change e 3,704 16 39ms 50ms 581ms 807ms 0 transport_latency_assumed tick_size_change f 3,704 8 44ms 61ms 504ms 725ms 0 transport_latency_assumed tick_size_change g 3,696 not meas. 79ms 110ms 1.1s 4.6s 0 transport_latency_assumed tick_size_change h 3,704 181 18ms 40ms 447ms 3.1s 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-11/17/2026-09-11T17.parquet sha256sum 2026-09-11T17.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.