Hour audit: 2026-09-22T08
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-22T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T08:00:00.000084212+00:00 · last event 2026-09-22T08:59:59.998730977+00:00
VOLUME 106,527,702 rows · 1,083,603,304 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 106,375,264 · h: 106,271,695 · f: 106,188,449 · e: 106,144,572 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 101,710,385 (95.48%) · h: 4,245,045 (3.98%) · f: 179,002 (0.17%) · e: 393,270 (0.37%) (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 106,527,702 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 8caaa135bf1a508059dff578155e4c8820bed7ce6d2e0a5ac3e4c5c044ed57ee
the corpus checksum ledger names this file with the same digest
joined 106,528,910 to merged 106,527,702, minus 1,208 (minus 0.0011%)
boundary drops 1,208 · 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-22T09:56:46Z as cefh
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-22T08:00Z to 2026-09-22T08:46ZThe 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 9,160,308 105,050,015 0-34 eb28b1d33c79b2f060b9563a81127e32ba622aa781e8a9f0c57b6ec7121de9a1 book 204,237 20,968,177 35-35 b3bed43cf0de7b2233254fcad99865635d4bedd1bfbb6f794e450bc449808f5d last_trade_price 58,003 3,322,806 36-36 ad4515c287643316fd02a0520c7ea7c5f5af25d576dc75b1549d47b930c6149e market_resolved 813 133,199 37-37 b09787b91b4f5a3a4191c21d2d7b0dc9e3ad4b873463f9d6d66188f733b5c646 new_market 889 94,585 38-38 0cc68cb2563063a964ddeef70fe1cd1763cce222354f9c2450f034e6eac60a30 price_change 97,100,060 952,699,276 39-409 37497c3bba9300ce79779ddbba9a3caa139c448e0521695c3eddde23e31beb5f tick_size_change 3,392 123,936 410-410 b3247756764dfb96d057e6567f2d7198155b2bb0bf8305b110a5e9fc3e07d82e EVENT MIX count share price_change 97,100,060 91.15% best_bid_ask 9,160,308 8.60% book 204,237 0.19% last_trade_price 58,003 0.05% tick_size_change 3,392 <0.01% new_market 889 <0.01% market_resolved 813 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,160,386 9,160,308 78 98 FULL book 204,303 204,237 66 37,124 FULL last_trade_price 58,003 58,003 0 0 FULL market_resolved 813 813 0 0 FULL new_market 889 889 0 0 FULL price_change 97,101,124 97,100,060 1,064 60 FULL tick_size_change 3,392 3,392 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,159,962 8,801,475 5ms 11ms 85ms 6.1s 0 transport_latency_assumed best_bid_ask e 9,153,353 25,760 39ms 48ms 223ms 10.5s 0 transport_latency_assumed best_bid_ask f 9,157,815 8,629 47ms 59ms 205ms 9.5s 0 transport_latency_assumed best_bid_ask h 9,158,207 324,444 18ms 28ms 119ms 22.0s 0 transport_latency_assumed book c 128,456 121,211 7ms 289ms 2.8d 115.4d 0 book_staleness book e 142,634 26,569 44ms 9.6min 14.9d 115.4d 0 book_staleness book f 142,979 25,590 52ms 9.3min 14.9d 115.4d 0 book_staleness book h 142,558 30,867 23ms 7.2min 14.9d 96.9d 0 book_staleness last_trade_price c 57,906 54,834 6ms 20ms 217ms 4.3s 0 transport_latency_assumed last_trade_price e 57,117 201 42ms 327ms 4.7s 10.7s 0 transport_latency_assumed last_trade_price f 57,527 65 50ms 305ms 4.9s 9.5s 0 transport_latency_assumed last_trade_price h 57,740 2,903 19ms 54ms 486ms 9.6s 0 transport_latency_assumed market_resolved c 801 733 5ms 20ms 53.6s 1.0min 0 transport_latency_assumed market_resolved e 801 31 40ms 354ms 54.4s 54.4s 0 transport_latency_assumed market_resolved f 801 not meas. 49ms 366ms 55.0s 55.1s 0 transport_latency_assumed market_resolved h 801 49 19ms 117ms 54.3s 54.4s 0 transport_latency_assumed new_market c 609 445 65ms 26.4s 59.4s 1.5min 0 transport_latency_assumed new_market e 609 109 169ms 17.5s 1.2min 1.7min 0 transport_latency_assumed new_market f 609 66 170ms 17.8s 36.9s 1.7min 0 transport_latency_assumed new_market h 609 269 102ms 17.6s 55.9s 1.7min 0 transport_latency_assumed price_change c 97,024,138 92,728,408 5ms 13ms 116ms 6.2s 0 transport_latency_assumed price_change e 96,786,666 340,588 40ms 66ms 1.8s 11.1s 0 transport_latency_assumed price_change f 96,825,326 144,652 48ms 75ms 826ms 9.6s 0 transport_latency_assumed price_change h 96,908,388 3,886,412 19ms 34ms 227ms 22.0s 0 transport_latency_assumed tick_size_change c 3,392 3,279 5ms 10ms 61ms 140ms 0 transport_latency_assumed tick_size_change e 3,392 12 39ms 57ms 111ms 699ms 0 transport_latency_assumed tick_size_change f 3,392 not meas. 47ms 56ms 96ms 196ms 0 transport_latency_assumed tick_size_change h 3,392 101 19ms 31ms 70ms 350ms 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-22/08/2026-09-22T08.parquet sha256sum 2026-09-22T08.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.