Hour audit: 2026-09-23T18
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-23T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T18:00:00.000201661+00:00 · last event 2026-09-23T18:59:59.999929231+00:00
VOLUME 124,066,530 rows · 1,404,304,960 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 120,682,238 · g: 115,853,403 · i: 111,399,237 · k: 110,967,703 · c: 90,092,269 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,809,117 (6.29%) · g: 282,880 (0.23%) · i: 3,230,228 (2.60%) · k: 31,793,517 (25.63%) · c: 80,950,788 (65.25%) (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 124,066,530 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 affe7c52b8be91b87cd37ef73c60b16f2991a1be1d160ecb49222d8676128800
the corpus checksum ledger names this file with the same digest
joined 124,074,721 to merged 124,066,530, minus 8,191 (minus 0.0066%)
boundary drops 8,191 · 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-24T04:16:47Z as cghik
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 eighteen minutes, 2026-09-23T18:06Z to 2026-09-23T18:24ZThe 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,323,876 128,446,338 0-39 2725f11afcac8a008efa8877e3fe6f4f1f1d2b5e543966e36e0dfaedd6dee202 book 3,245,747 126,616,791 40-52 4b168a605256250698707ecaa12d98c003bbc880a2b1c2774ff611ccb127ebbb last_trade_price 63,993 3,636,657 53-53 6bffdd928ed8c62ad4cbe7dfffa3326da46451e1f2147bee095e4a03edd1609a market_resolved 953 103,885 54-54 cf86df5150dcfcd58ce8ca97a29afbb1cf3fb6263dfa0c54de65444beee2e77e new_market 2,083 189,969 55-55 d966782a97ed6b60b48fea5a1afa873513254289108eb925cbd173a8c3c151d6 price_change 110,426,194 1,143,762,265 56-477 3492a0c24756482a1876494002010fb92a91be006cfb17b32a51fda571012049 tick_size_change 3,684 135,666 478-478 0edf2e8074dc285033d15760e4253317419cfe50bb7a58fb5aa5f89c19f563c3 EVENT MIX count share price_change 110,426,194 89.01% best_bid_ask 10,323,876 8.32% book 3,245,747 2.62% last_trade_price 63,993 0.05% tick_size_change 3,684 <0.01% new_market 2,083 <0.01% market_resolved 953 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,324,890 10,323,876 1,014 5,205 FULL book 3,246,151 3,245,747 404 183,112 FULL last_trade_price 63,994 63,993 1 725 FULL market_resolved 953 953 0 61 FULL new_market 2,083 2,083 0 1 FULL price_change 110,432,966 110,426,194 6,772 785 FULL tick_size_change 3,684 3,684 0 306 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,476,087 6,763,642 5ms 16ms 131ms 9.4s 0 transport_latency_assumed best_bid_ask g 9,911,728 7,102 79ms 138ms 827ms 31.8s 0 transport_latency_assumed best_bid_ask h 10,311,401 632,977 18ms 39ms 284ms 23.4s 0 transport_latency_assumed best_bid_ask i 9,517,386 241,410 23ms 36ms 173ms 7.8s 0 transport_latency_assumed best_bid_ask k 9,470,447 2,678,745 13ms 22ms 122ms 7.4s 0 transport_latency_assumed book c 2,521,658 2,284,854 4.0min 4.2d 43.0d 116.9d 0 book_staleness book g 583,040 171,711 1.3min 2.9d 38.0d 116.9d 0 book_staleness book h 152,904 19,111 29ms 4.0min 5.1d 116.9d 0 book_staleness book i 1,003,544 277,238 1.9min 3.2d 42.0d 116.8d 0 book_staleness book k 968,388 492,833 1.8min 3.2d 42.0d 116.9d 0 book_staleness last_trade_price c 46,640 41,277 6ms 28ms 235ms 2.3s 0 transport_latency_assumed last_trade_price g 59,266 58 100ms 2.1s 18.1s 31.6s 0 transport_latency_assumed last_trade_price h 63,073 3,255 21ms 179ms 977ms 8.1s 0 transport_latency_assumed last_trade_price i 59,414 1,359 27ms 276ms 1.7s 3.0s 0 transport_latency_assumed last_trade_price k 59,296 18,044 14ms 39ms 222ms 1.6s 0 transport_latency_assumed market_resolved c 706 581 13ms 10.0min 15.8min 15.8min 0 transport_latency_assumed market_resolved g 611 24 89ms 47.0s 5.7min 5.7min 0 transport_latency_assumed market_resolved h 603 129 20ms 23.8s 1.0min 1.0min 0 transport_latency_assumed market_resolved i 636 37 25ms 45.3s 5.6min 5.6min 0 transport_latency_assumed market_resolved k 578 182 14ms 101ms 4.0min 4.7min 0 transport_latency_assumed new_market c 1,578 795 174ms 12.0min 12.6min 314.9d 0 transport_latency_assumed new_market g 1,169 167 300ms 18.1s 2.4min 5.1min 0 transport_latency_assumed new_market h 1,165 297 111ms 11.7s 49.8s 314.9d 0 transport_latency_assumed new_market i 1,181 333 116ms 20.5s 4.8min 315.0d 0 transport_latency_assumed new_market k 1,167 491 78ms 9.5s 39.8s 315.0d 0 transport_latency_assumed price_change c 80,042,960 71,857,230 5ms 20ms 163ms 9.4s 0 transport_latency_assumed price_change g 105,293,981 103,818 81ms 217ms 6.3s 32.0s 0 transport_latency_assumed price_change h 110,149,408 7,153,189 19ms 50ms 431ms 23.9s 0 transport_latency_assumed price_change i 100,813,572 2,709,822 23ms 50ms 364ms 7.9s 0 transport_latency_assumed price_change k 100,464,275 28,602,135 13ms 26ms 164ms 7.9s 0 transport_latency_assumed tick_size_change c 2,640 2,409 5ms 12ms 89ms 277ms 0 transport_latency_assumed tick_size_change g 3,608 not meas. 78ms 97ms 273ms 486ms 0 transport_latency_assumed tick_size_change h 3,684 159 19ms 31ms 71ms 1.7s 0 transport_latency_assumed tick_size_change i 3,504 29 23ms 29ms 77ms 316ms 0 transport_latency_assumed tick_size_change k 3,552 1,087 13ms 18ms 52ms 1.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-23/18/2026-09-23T18.parquet sha256sum 2026-09-23T18.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.