Hour audit: 2026-09-23T10
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-23T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T10:00:00.003065009+00:00 · last event 2026-09-23T10:59:59.999925329+00:00
VOLUME 120,917,392 rows · 1,308,606,963 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured i: 119,886,775 · h: 119,452,238 · k: 114,742,096 · f: 114,200,935 · c: 110,390,243 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,814,549 (1.50%) · h: 3,101,979 (2.57%) · k: 16,243,004 (13.43%) · f: 232,789 (0.19%) · c: 99,525,071 (82.31%) (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 120,917,392 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 05ef92242df25af6e1788a7f36de2008235eb405b9c103c84fc1031c69c6789d
the corpus checksum ledger names this file with the same digest
joined 120,918,570 to merged 120,917,392, minus 1,178 (minus 0.0010%)
boundary drops 1,178 · 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-23T13:08:56Z as cfhik
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 11,179,257 131,448,559 0-42 894745f61ecefc36978665f6302ac846467c5b5c0e97b05d9c38e93f70cbce11 book 1,291,061 79,876,582 43-47 d3212ffff336e96242b9d6233813521e01b95d8a00ffadf04315ab0df764bb6b last_trade_price 56,512 3,160,339 48-48 39f73bb53bb49c7cebd31cf00091590dd5340715591b4986a4f1913f14513901 market_resolved 963 128,623 49-49 0467506be0006e8b200a43348ba560da3eb52deba4475ee9ed74b5b19614445e new_market 3,053 291,868 50-50 17bbb9e82901b6cdf49582a3a583e06f216497ea69692f7720b8ab8fe9e17745 price_change 108,383,262 1,092,204,766 51-464 7b24afdcb44b1666a9447030ee89fc0a451e9a9b88841e4d75c4f91b72c92395 tick_size_change 3,284 121,550 465-465 ab56ced011b6f0d45eb60e382de306f585ad61d6e5e066f9cf222ca6094506ca EVENT MIX count share price_change 108,383,262 89.63% best_bid_ask 11,179,257 9.25% book 1,291,061 1.07% last_trade_price 56,512 0.05% tick_size_change 3,284 <0.01% new_market 3,053 <0.01% market_resolved 963 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,179,407 11,179,257 150 1,745 FULL book 1,291,105 1,291,061 44 185,469 FULL last_trade_price 56,512 56,512 0 213 FULL market_resolved 963 963 0 118 FULL new_market 3,053 3,053 0 2 FULL price_change 108,384,246 108,383,262 984 360 FULL tick_size_change 3,284 3,284 0 83 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,231,702 9,306,676 5ms 17ms 185ms 15.9s 0 transport_latency_assumed best_bid_ask f 10,641,455 5,981 50ms 72ms 335ms 27.3s 0 transport_latency_assumed best_bid_ask h 11,174,344 262,252 19ms 36ms 286ms 57.7s 0 transport_latency_assumed best_bid_ask i 11,172,930 147,398 22ms 34ms 178ms 10.0s 0 transport_latency_assumed best_bid_ask k 10,654,067 1,456,950 13ms 23ms 134ms 6.4s 0 transport_latency_assumed book c 907,321 783,022 9.3min 3.8d 41.6d 116.5d 0 book_staleness book f 524,277 150,759 5.1min 2.6d 38.2d 116.5d 0 book_staleness book h 140,800 15,614 28ms 7.0min 15.7d 116.5d 0 book_staleness book i 376,880 131,505 1.9min 1.6d 31.9d 116.5d 0 book_staleness book k 518,874 210,161 4.2min 2.6d 38.7d 116.5d 0 book_staleness last_trade_price c 50,435 44,875 6ms 34ms 329ms 4.6s 0 transport_latency_assumed last_trade_price f 52,387 89 55ms 489ms 12.5s 27.3s 0 transport_latency_assumed last_trade_price h 56,297 1,964 21ms 157ms 729ms 25.3s 0 transport_latency_assumed last_trade_price i 56,180 791 26ms 245ms 1.9s 10.0s 0 transport_latency_assumed last_trade_price k 52,315 8,793 14ms 54ms 289ms 855ms 0 transport_latency_assumed market_resolved c 784 711 6ms 2.3min 5.3min 6.8min 0 transport_latency_assumed market_resolved f 764 not meas. 51ms 50.7s 4.6min 4.6min 0 transport_latency_assumed market_resolved h 782 88 20ms 47.0s 55.7s 59.8s 0 transport_latency_assumed market_resolved i 782 23 23ms 46.7s 55.7s 1.0min 0 transport_latency_assumed market_resolved k 682 141 13ms 61ms 57.6s 2.3min 0 transport_latency_assumed new_market c 1,879 828 143ms 25.0s 4.1min 44.9min 0 transport_latency_assumed new_market f 1,877 256 205ms 19.5s 51.0s 1.7min 0 transport_latency_assumed new_market h 1,877 630 176ms 22.3s 42.4s 1.4min 0 transport_latency_assumed new_market i 1,877 528 147ms 22.5s 38.1s 1.7min 0 transport_latency_assumed new_market k 1,877 811 126ms 22.0s 36.4s 1.3min 0 transport_latency_assumed price_change c 99,195,070 89,386,106 5ms 21ms 215ms 15.9s 0 transport_latency_assumed price_change f 102,976,963 75,704 50ms 98ms 1.1s 27.3s 0 transport_latency_assumed price_change h 108,074,854 2,821,381 19ms 47ms 416ms 57.8s 0 transport_latency_assumed price_change i 108,274,842 1,534,272 22ms 48ms 385ms 10.0s 0 transport_latency_assumed price_change k 103,511,061 14,565,799 13ms 29ms 184ms 7.2s 0 transport_latency_assumed tick_size_change c 3,052 2,853 5ms 11ms 67ms 113ms 0 transport_latency_assumed tick_size_change f 3,212 not meas. 50ms 79ms 247ms 686ms 0 transport_latency_assumed tick_size_change h 3,284 50 19ms 57ms 473ms 3.3s 0 transport_latency_assumed tick_size_change i 3,284 32 22ms 53ms 108ms 1.4s 0 transport_latency_assumed tick_size_change k 3,220 349 13ms 19ms 64ms 207ms 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/10/2026-09-23T10.parquet sha256sum 2026-09-23T10.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.