Hour audit: 2026-09-10T04
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-10T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T04:00:00.000029681+00:00 · last event 2026-09-10T04:59:59.999973970+00:00
VOLUME 107,528,037 rows · 1,106,586,017 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 107,164,472 · f: 107,035,373 · h: 107,005,795 · e: 106,935,360 · c: 102,366,357 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 189,071 (0.18%) · f: 291,984 (0.27%) · h: 9,162,200 (8.52%) · e: 912,499 (0.85%) · c: 96,972,283 (90.18%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 107,528,037 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b06ec7969a6b6a06b09f32b293b09fed1da4f945ce4f9f66ec375a6a86838de9
the corpus checksum ledger names this file with the same digest
joined 107,530,526 to merged 107,528,037, minus 2,489 (minus 0.0023%)
boundary drops 2,489 · 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-10T06:34:54Z 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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The 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,625,718 107,565,772 0-36 a44e02efb03ac80436681a29184c63ce5b1eabb2c8d5a56a884c977cab35220b book 572,622 57,864,356 37-39 4418e39fa832b3542191e8643e1b05c1dfd5eeb08e8f7e68f8b69503a2e60bf7 last_trade_price 48,821 2,751,313 40-40 17a81533e94509abf83e4fe9dfa98c4fb1f04d4558132901cf810cb6e6d8b32c market_resolved 1,458 219,756 41-41 4c4bc9cc00d22a457667e5ec99c6b2c5f3853f008adbffeae79ff0b21f0b87e6 new_market 2,530 274,676 42-42 a04400e443b429db298971c5710d98d55e0804dd585661662d5122d56a861f7a price_change 97,273,028 936,541,668 43-414 19c4042944b68fbad7c687c7f57ef02093ca785b003302169814d6e76fe87ef4 tick_size_change 3,860 140,813 415-415 830951a1fc5e8bac21764dc133d96287ba1807db9543bc8f1814d2c6eedae528 EVENT MIX count share price_change 97,273,028 90.46% best_bid_ask 9,625,718 8.95% book 572,622 0.53% last_trade_price 48,821 0.05% tick_size_change 3,860 <0.01% new_market 2,530 <0.01% market_resolved 1,458 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,625,879 9,625,718 161 721 FULL book 572,843 572,622 221 193,293 FULL last_trade_price 48,824 48,821 3 45 FULL market_resolved 1,458 1,458 0 2 FULL new_market 2,530 2,530 0 3 FULL price_change 97,275,132 97,273,028 2,104 372 FULL tick_size_change 3,860 3,860 0 21 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,143,766 8,669,656 5ms 12ms 234ms 9.0s 0 transport_latency_assumed best_bid_ask e 9,623,801 85,354 39ms 48ms 242ms 4.7s 0 transport_latency_assumed best_bid_ask f 9,623,740 26,697 46ms 60ms 284ms 5.3s 0 transport_latency_assumed best_bid_ask g 9,620,962 3,385 79ms 114ms 554ms 16.2s 0 transport_latency_assumed best_bid_ask h 9,624,201 840,626 17ms 32ms 428ms 35.3s 0 transport_latency_assumed book c 496,276 403,038 7.2min 19.5h 29.4d 103.2d 0 book_staleness book e 105,228 2,928 41ms 212ms 15.1s 84.7d 0 book_staleness book f 104,558 1,432 49ms 219ms 3.3s 84.7d 0 book_staleness book g 265,453 153,819 39.7s 12.3h 18.6d 103.2d 0 book_staleness book h 105,550 11,405 22ms 124ms 6.2min 84.8d 0 book_staleness last_trade_price c 46,607 43,488 10ms 53ms 319ms 6.5s 0 transport_latency_assumed last_trade_price e 48,784 616 47ms 156ms 1.3s 4.9s 0 transport_latency_assumed last_trade_price f 48,796 201 56ms 176ms 1.2s 5.0s 0 transport_latency_assumed last_trade_price g 48,720 31 95ms 304ms 7.0s 14.5s 0 transport_latency_assumed last_trade_price h 48,701 4,485 23ms 89ms 601ms 7.9s 0 transport_latency_assumed market_resolved c 1,397 1,313 5ms 46ms 5.9min 5.9min 0 transport_latency_assumed market_resolved e 1,375 52 41ms 256ms 39.9s 1.0min 0 transport_latency_assumed market_resolved f 1,375 5 49ms 238ms 40.1s 1.0min 0 transport_latency_assumed market_resolved g 1,375 2 90ms 426ms 42.0s 1.3min 0 transport_latency_assumed market_resolved h 1,375 86 18ms 104ms 40.2s 1.0min 0 transport_latency_assumed new_market c 1,799 1,015 102ms 18.7s 1.2min 1.6h 0 transport_latency_assumed new_market e 1,796 340 166ms 19.6s 45.9s 43.6min 0 transport_latency_assumed new_market f 1,799 306 193ms 20.0s 44.2s 3.1d 0 transport_latency_assumed new_market g 1,796 212 337ms 19.3s 57.8s 14.4min 0 transport_latency_assumed new_market h 1,796 657 158ms 19.5s 1.0min 8.5min 0 transport_latency_assumed price_change c 92,672,732 87,850,156 5ms 13ms 230ms 9.0s 0 transport_latency_assumed price_change e 97,150,516 823,181 39ms 53ms 319ms 5.5s 0 transport_latency_assumed price_change f 97,251,245 263,339 46ms 66ms 366ms 5.3s 0 transport_latency_assumed price_change g 97,222,310 31,622 81ms 129ms 776ms 16.9s 0 transport_latency_assumed price_change h 97,220,312 8,304,730 17ms 35ms 413ms 42.0s 0 transport_latency_assumed tick_size_change c 3,780 3,617 5ms 12ms 102ms 988ms 0 transport_latency_assumed tick_size_change e 3,860 28 39ms 54ms 205ms 592ms 0 transport_latency_assumed tick_size_change f 3,860 4 46ms 59ms 248ms 678ms 0 transport_latency_assumed tick_size_change g 3,856 not meas. 80ms 99ms 583ms 878ms 0 transport_latency_assumed tick_size_change h 3,860 211 17ms 36ms 293ms 5.5s 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-10/04/2026-09-10T04.parquet sha256sum 2026-09-10T04.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.