Hour audit: 2026-09-10T20
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-10T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T20:00:00.000119425+00:00 · last event 2026-09-10T20:59:59.999953218+00:00
VOLUME 113,077,509 rows · 1,212,036,863 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 110,941,632 · g: 110,915,806 · e: 110,797,783 · h: 110,787,007 · c: 89,231,234 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 621,876 (0.55%) · g: 49,859 (0.04%) · e: 1,583,241 (1.40%) · h: 26,325,935 (23.28%) · c: 84,496,598 (74.72%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 aefd9dda3cfc88a8ab4ce29c7e400140fece56a1b2acca420591c32fe944f7aa
the corpus checksum ledger names this file with the same digest
joined 113,082,335 to merged 113,077,509, minus 4,826 (minus 0.0043%)
boundary drops 4,826 · 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-10T22:01:15Z 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 10,622,386 119,898,309 0-40 57ecd99bf7592ae404f1072054c02d29223797e5c221a8e372233cb255ae5cff book 2,163,885 93,326,235 41-49 8ddc679d67e6029549e059cda61ead64c233920659ea9cec325d3532addc0b30 last_trade_price 56,327 3,226,649 50-50 f4a294bbcafd6286f3ba81b0eae47da7451d94985901499376d4ad44d9cc6e08 market_resolved 1,722 190,492 51-51 d920bd6367c1014d5b2dd02c5399a2d2c21507cd897b7f2f780abe89c8a9e279 new_market 3,241 273,595 52-52 f86c708d228d4dca45da74a45d69fffcfce0ea9417248363ec6f5f26e36810b6 price_change 100,227,264 993,731,889 53-435 594bd21daadecc34a3f223d9a638b0fcdcad546cdf5e8d77fe32986c9a748e22 tick_size_change 2,684 100,139 436-436 14c44f40815d1a5934be7179f4d4aed0f7558577a58421db0d518259fdf36f5f EVENT MIX count share price_change 100,227,264 88.64% best_bid_ask 10,622,386 9.39% book 2,163,885 1.91% last_trade_price 56,327 0.05% new_market 3,241 <0.01% tick_size_change 2,684 <0.01% market_resolved 1,722 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,622,723 10,622,386 337 4,829 FULL book 2,163,907 2,163,885 22 200,311 FULL last_trade_price 56,328 56,327 1 430 FULL market_resolved 1,722 1,722 0 35 FULL new_market 3,241 3,241 0 0 FULL price_change 100,231,730 100,227,264 4,466 3,558 FULL tick_size_change 2,684 2,684 0 126 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,364,851 7,928,254 5ms 13ms 120ms 8.2s 0 transport_latency_assumed best_bid_ask e 10,620,139 147,546 40ms 50ms 242ms 6.1s 0 transport_latency_assumed best_bid_ask f 10,619,853 52,528 45ms 58ms 265ms 15.2s 0 transport_latency_assumed best_bid_ask g 10,618,556 3,658 80ms 111ms 563ms 22.2s 0 transport_latency_assumed best_bid_ask h 10,620,656 2,490,400 18ms 27ms 264ms 52.2s 0 transport_latency_assumed book c 2,129,865 2,121,053 33.8min 1.3d 30.1d 103.9d 0 book_staleness book e 121,021 4,401 43ms 252ms 34.6s 102.3d 0 book_staleness book f 121,921 2,626 48ms 331ms 44.7min 85.4d 0 book_staleness book g 130,394 4,625 91ms 3.5s 1.0d 103.9d 0 book_staleness book h 121,395 31,180 22ms 118ms 7.7min 85.4d 0 book_staleness last_trade_price c 42,895 40,354 11ms 49ms 294ms 8.0s 0 transport_latency_assumed last_trade_price e 56,191 1,071 52ms 195ms 2.1s 6.1s 0 transport_latency_assumed last_trade_price f 56,133 485 58ms 214ms 1.9s 15.2s 0 transport_latency_assumed last_trade_price g 55,997 74 98ms 368ms 4.8s 22.5s 0 transport_latency_assumed last_trade_price h 56,142 14,343 24ms 94ms 574ms 35.3s 0 transport_latency_assumed market_resolved c 1,450 1,391 8ms 12.2min 19.0min 19.0min 0 transport_latency_assumed market_resolved e 1,136 32 42ms 217ms 52.5s 57.9s 0 transport_latency_assumed market_resolved f 1,136 14 47ms 251ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 1,136 2 87ms 376ms 58.0s 1.0min 0 transport_latency_assumed market_resolved h 1,136 283 19ms 109ms 57.9s 1.0min 0 transport_latency_assumed new_market c 2,445 1,661 3.0min 9.1min 15.2min 7.0d 0 transport_latency_assumed new_market e 1,661 422 181ms 20.0s 1.4min 7.0d 0 transport_latency_assumed new_market f 1,661 268 213ms 36.4s 1.5min 3.4min 0 transport_latency_assumed new_market g 1,661 198 301ms 27.5s 1.4min 7.0d 0 transport_latency_assumed new_market h 1,661 692 136ms 28.0s 1.4min 5.4min 0 transport_latency_assumed price_change c 78,687,548 74,401,782 6ms 14ms 134ms 12.6s 0 transport_latency_assumed price_change e 99,994,951 1,429,748 40ms 59ms 373ms 9.0s 0 transport_latency_assumed price_change f 100,138,244 565,944 45ms 68ms 405ms 15.3s 0 transport_latency_assumed price_change g 100,105,378 41,301 81ms 134ms 824ms 22.6s 0 transport_latency_assumed price_change h 99,983,333 23,788,489 18ms 31ms 287ms 53.1s 0 transport_latency_assumed tick_size_change c 2,180 2,103 6ms 11ms 67ms 242ms 0 transport_latency_assumed tick_size_change e 2,684 21 40ms 51ms 276ms 821ms 0 transport_latency_assumed tick_size_change f 2,684 11 45ms 59ms 337ms 584ms 0 transport_latency_assumed tick_size_change g 2,684 1 80ms 115ms 642ms 1.0s 0 transport_latency_assumed tick_size_change h 2,684 548 18ms 26ms 240ms 388ms 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/20/2026-09-10T20.parquet sha256sum 2026-09-10T20.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.