Hour audit: 2026-09-08T22
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-08T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T22:00:00.000006718+00:00 · last event 2026-09-08T22:59:59.999987107+00:00
VOLUME 87,559,933 rows · 856,448,819 bytes (816.77 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 87,512,229 · f: 87,444,959 · g: 87,436,938 · h: 87,426,693 · e: 87,368,308 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 84,288,286 (96.26%) · f: 155,511 (0.18%) · g: 33,039 (0.04%) · h: 2,764,101 (3.16%) · e: 318,996 (0.36%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 87,559,933 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 25fa4f53138a79159e21ecb21b4d5442dc9135e821c68097ce811f31047fd734
the corpus checksum ledger names this file with the same digest
joined 87,561,392 to merged 87,559,933, minus 1,459 (minus 0.0017%)
boundary drops 1,459 · 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-08T23:53:43Z 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 that overran, on a market this archive does not record, 2026-09-08T22:02Z to 2026-09-09T00:38ZThe 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 8,393,834 92,613,926 0-32 230f59ef0a9e7a1b405f1f7dd82caef457bf06185295967702ad34d3626ed844 book 142,916 13,984,567 33-33 bcd8f2ff95efc231f21e29c129853264767d1ccd0e0224805e5e95c39df51159 last_trade_price 58,052 3,241,575 34-34 7e42d46dac193e439a5e49c4ddfd2351362e1f40fcdecee65a0776eaa1eaf060 market_resolved 1,905 308,860 35-35 24f685a956450f0810857faade32d2f9c53a450cf4b47f446f562a64da2e0001 new_market 2,242 227,931 36-36 7ece6d87457855f68b1290f86db4288059bbdcabf0e264be0e0f1c2af8901118 price_change 78,958,852 744,991,226 37-338 b77cdc7dd1f54f6bda3faf944215102778260a42cc88b0206982a6cd41cbb3e8 tick_size_change 2,132 77,723 339-339 6dacb1d1fa99054ad57d0928b5ae5781b83102277cd11f9ee4b1cea524da2e8a EVENT MIX count share price_change 78,958,852 90.18% best_bid_ask 8,393,834 9.59% book 142,916 0.16% last_trade_price 58,052 0.07% new_market 2,242 <0.01% tick_size_change 2,132 <0.01% market_resolved 1,905 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,393,942 8,393,834 108 169 FULL book 142,916 142,916 0 8,751 FULL last_trade_price 58,055 58,052 3 1 FULL market_resolved 1,905 1,905 0 0 FULL new_market 2,242 2,242 0 0 FULL price_change 78,960,200 78,958,852 1,348 342 FULL tick_size_change 2,132 2,132 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,392,916 8,096,017 4ms 9ms 120ms 30.5s 0 transport_latency_assumed best_bid_ask e 8,392,096 29,109 39ms 47ms 209ms 5.1s 0 transport_latency_assumed best_bid_ask f 8,392,068 13,991 46ms 55ms 218ms 4.6s 0 transport_latency_assumed best_bid_ask g 8,390,234 1,033 86ms 106ms 425ms 12.5s 0 transport_latency_assumed best_bid_ask h 8,392,848 253,684 17ms 22ms 187ms 40.2s 0 transport_latency_assumed book c 124,348 117,402 7ms 36ms 7.7min 83.5d 0 book_staleness book e 123,080 1,904 42ms 290ms 3.9s 83.5d 0 book_staleness book f 122,808 1,273 49ms 312ms 3.7s 76.5d 0 book_staleness book g 137,622 16,151 96ms 24.7s 1.4d 83.5d 0 book_staleness book h 122,963 6,186 21ms 81ms 2.9s 35.2d 0 book_staleness last_trade_price c 57,900 55,416 9ms 39ms 236ms 5.0s 0 transport_latency_assumed last_trade_price e 58,014 268 46ms 238ms 2.9s 5.1s 0 transport_latency_assumed last_trade_price f 58,016 132 53ms 255ms 3.0s 5.0s 0 transport_latency_assumed last_trade_price g 57,738 16 100ms 503ms 7.1s 12.3s 0 transport_latency_assumed last_trade_price h 57,970 2,220 22ms 71ms 458ms 10.5s 0 transport_latency_assumed market_resolved c 1,880 1,805 4ms 11ms 270ms 2.1s 0 transport_latency_assumed market_resolved e 1,880 31 45ms 205ms 45.0s 59.1s 0 transport_latency_assumed market_resolved f 1,880 3 59ms 216ms 45.0s 59.1s 0 transport_latency_assumed market_resolved g 1,880 1 100ms 408ms 1.1s 1.7s 0 transport_latency_assumed market_resolved h 1,880 65 22ms 83ms 593ms 1.0min 0 transport_latency_assumed new_market c 1,445 745 96ms 35.1s 1.3min 2.0min 0 transport_latency_assumed new_market e 1,445 350 173ms 35.9s 1.4min 4.8min 0 transport_latency_assumed new_market f 1,445 248 164ms 35.8s 1.2min 2.0min 0 transport_latency_assumed new_market g 1,445 194 268ms 34.5s 1.2min 2.0min 0 transport_latency_assumed new_market h 1,445 705 108ms 33.7s 1.2min 1.9min 0 transport_latency_assumed price_change c 78,931,608 76,014,805 5ms 10ms 139ms 30.5s 0 transport_latency_assumed price_change e 78,789,661 287,330 39ms 54ms 338ms 5.1s 0 transport_latency_assumed price_change f 78,866,610 139,864 46ms 62ms 336ms 4.6s 0 transport_latency_assumed price_change g 78,845,887 15,644 87ms 125ms 672ms 13.2s 0 transport_latency_assumed price_change h 78,847,455 2,501,209 18ms 25ms 228ms 42.5s 0 transport_latency_assumed tick_size_change c 2,132 2,096 5ms 9ms 32ms 125ms 0 transport_latency_assumed tick_size_change e 2,132 4 39ms 45ms 148ms 260ms 0 transport_latency_assumed tick_size_change f 2,132 not meas. 46ms 51ms 116ms 191ms 0 transport_latency_assumed tick_size_change g 2,132 not meas. 84ms 100ms 171ms 356ms 0 transport_latency_assumed tick_size_change h 2,132 32 17ms 26ms 82ms 2.0s 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-08/22/2026-09-08T22.parquet sha256sum 2026-09-08T22.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.