Hour audit: 2026-09-10T18
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-10T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T18:00:00.000027097+00:00 · last event 2026-09-10T18:59:59.999967772+00:00
VOLUME 109,835,717 rows · 1,193,799,454 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 108,476,386 · f: 108,459,583 · g: 108,442,613 · h: 108,428,500 · c: 95,604,684 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,270,156 (1.16%) · f: 477,099 (0.43%) · g: 82,440 (0.08%) · h: 20,498,680 (18.66%) · c: 87,507,342 (79.67%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 9ef786e6b261ffb2dc11d06e86c8b2f1686adbe14ed79cf22536cb06dad64ca3
the corpus checksum ledger names this file with the same digest
joined 109,838,705 to merged 109,835,717, minus 2,988 (minus 0.0027%)
boundary drops 2,988 · 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-10T19:58:37Z 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,579,558 120,741,645 0-40 63815b71b994df3552f4877c1bbe4fcc766e1c5d2f8970d77670b3bf11244123 book 1,388,731 81,360,447 41-46 3893f504648cb1153ce1dbbfa2ab8e2b64244d8b84e7b771c2b3f16d50c2243b last_trade_price 65,558 3,718,776 47-47 aecb2c96a202673db3bf92b01c72081f7bc98495d59f7395f5ba60e95ece357e market_resolved 1,831 245,631 48-48 fb16516cfc5fd137b285ed98a04072f3961ad36a0486fce82584ab62ab10ffed new_market 3,132 328,241 49-49 dec4345028fa00fc8c89d95d06a24cb090671b096ba033a2b8eb7a9bb322a972 price_change 97,792,803 985,998,052 50-423 bd734bc4f54dd4ab7c08745206423e01cbb66343e35482289810ef534db81f4c tick_size_change 4,104 152,435 424-424 e7439e3650d74c6e1d771bc2210ea659f5d91d124bcbcc07676f4757423b1194 EVENT MIX count share price_change 97,792,803 89.04% best_bid_ask 10,579,558 9.63% book 1,388,731 1.26% last_trade_price 65,558 0.06% tick_size_change 4,104 <0.01% new_market 3,132 <0.01% market_resolved 1,831 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,579,858 10,579,558 300 1,559 FULL book 1,388,751 1,388,731 20 194,334 FULL last_trade_price 65,558 65,558 0 233 FULL market_resolved 1,831 1,831 0 1 FULL new_market 3,132 3,132 0 6 FULL price_change 97,795,471 97,792,803 2,668 1,065 FULL tick_size_change 4,104 4,104 0 89 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,215,216 8,408,278 6ms 21ms 196ms 6.3s 0 transport_latency_assumed best_bid_ask e 10,576,229 124,769 40ms 51ms 257ms 15.7s 0 transport_latency_assumed best_bid_ask f 10,576,577 43,116 44ms 60ms 266ms 17.1s 0 transport_latency_assumed best_bid_ask g 10,572,200 3,417 80ms 118ms 577ms 18.9s 0 transport_latency_assumed best_bid_ask h 10,575,820 1,999,978 18ms 31ms 284ms 41.5s 0 transport_latency_assumed book c 1,324,406 1,304,726 20.3min 1.3d 30.0d 103.9d 0 book_staleness book e 151,379 9,714 44ms 3.1s 23.2h 103.9d 0 book_staleness book f 154,336 7,875 50ms 7.8s 1.4d 85.3d 0 book_staleness book g 220,064 36,113 215ms 6.6h 16.0d 103.8d 0 book_staleness book h 146,640 30,303 24ms 320ms 12.5h 85.4d 0 book_staleness last_trade_price c 56,253 51,191 12ms 61ms 385ms 5.2s 0 transport_latency_assumed last_trade_price e 65,348 1,070 54ms 233ms 5.3s 15.7s 0 transport_latency_assumed last_trade_price f 65,401 522 61ms 222ms 5.3s 17.2s 0 transport_latency_assumed last_trade_price g 64,925 161 98ms 383ms 6.7s 18.9s 0 transport_latency_assumed last_trade_price h 65,161 12,614 25ms 87ms 727ms 7.2s 0 transport_latency_assumed market_resolved c 1,667 1,538 7ms 5.4min 11.6min 11.6min 0 transport_latency_assumed market_resolved e 1,486 17 46ms 257ms 1.0s 1.1min 0 transport_latency_assumed market_resolved f 1,486 10 51ms 272ms 862ms 1.1min 0 transport_latency_assumed market_resolved g 1,486 1 95ms 519ms 1.4s 56.6s 0 transport_latency_assumed market_resolved h 1,486 265 26ms 103ms 2.8s 1.1min 0 transport_latency_assumed new_market c 2,179 1,022 99ms 35.7s 7.2min 7.2min 0 transport_latency_assumed new_market e 2,101 561 151ms 21.3s 1.9min 2.6min 0 transport_latency_assumed new_market f 2,103 216 173ms 22.8s 2.0min 2.6min 0 transport_latency_assumed new_market g 2,098 316 295ms 25.3s 1.9min 2.7min 0 transport_latency_assumed new_market h 2,100 1,017 101ms 22.3s 1.8min 2.3min 0 transport_latency_assumed price_change c 85,001,207 77,737,071 6ms 22ms 204ms 6.5s 0 transport_latency_assumed price_change e 97,675,739 1,133,987 40ms 62ms 461ms 15.7s 0 transport_latency_assumed price_change f 97,655,576 425,338 45ms 71ms 402ms 17.2s 0 transport_latency_assumed price_change g 97,577,744 42,427 81ms 149ms 932ms 19.0s 0 transport_latency_assumed price_change h 97,633,189 18,453,980 18ms 35ms 301ms 42.5s 0 transport_latency_assumed tick_size_change c 3,756 3,516 6ms 17ms 329ms 1.0s 0 transport_latency_assumed tick_size_change e 4,104 38 40ms 58ms 327ms 1.5s 0 transport_latency_assumed tick_size_change f 4,104 22 44ms 83ms 349ms 2.0s 0 transport_latency_assumed tick_size_change g 4,096 5 80ms 159ms 649ms 8.5s 0 transport_latency_assumed tick_size_change h 4,104 523 18ms 40ms 582ms 2.6s 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/18/2026-09-10T18.parquet sha256sum 2026-09-10T18.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.