Hour audit: 2026-09-10T01
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-10T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T01:00:00.000169368+00:00 · last event 2026-09-10T01:59:59.999951800+00:00
VOLUME 122,861,376 rows · 1,312,110,493 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 121,005,273 · e: 120,995,547 · g: 115,811,228 · f: 115,508,527 · c: 104,398,728 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 20,860,959 (16.98%) · e: 1,285,228 (1.05%) · g: 93,204 (0.08%) · f: 441,870 (0.36%) · c: 100,180,115 (81.54%) (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 122,861,376 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9b01e457c8949d59f40fea8ae81c1f674fb93dae75fffef7b90ab782a13429c9
the corpus checksum ledger names this file with the same digest
joined 122,866,150 to merged 122,861,376, minus 4,774 (minus 0.0039%)
boundary drops 4,774 · 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-10T03:06:04Z 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 12,802,013 140,690,494 0-48 c91eb90a8c3530535b4f17575e9c701c3400fd1606936800ed5a74389361c683 book 1,848,073 87,879,019 49-56 b77eeb207caad5b1e72bad416f4dcbf0fc7293558fc80460a4a613f908ab4b1c last_trade_price 51,756 2,949,000 57-57 91f4f5868cb19abd00ad22cc5e1830517e67df7be25aec37050d6a686e89ed97 market_resolved 2,155 307,755 58-58 7d20d7e09fada4eb3f276150e9fef18d263f0266846e76be09a7edcebc1bec55 new_market 1,460 153,364 59-59 6085661d78ef601aa1bc8589f2c55b30f293330355dc9f8340c86eb488dcb02c price_change 108,150,455 1,078,532,201 60-472 c54551fbd7bb6dcf663497afd7afad10db259516860bdd8b4df90dd1f5c9dc05 tick_size_change 5,464 200,969 473-473 76598930edb818c8fca7fa86c8ac18adee60673b9c2f4459b1287c3ef5efe47d EVENT MIX count share price_change 108,150,455 88.03% best_bid_ask 12,802,013 10.42% book 1,848,073 1.50% last_trade_price 51,756 0.04% tick_size_change 5,464 <0.01% market_resolved 2,155 <0.01% new_market 1,460 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,802,281 12,802,013 268 3,309 FULL book 1,849,661 1,848,073 1,588 197,948 FULL last_trade_price 51,756 51,756 0 350 FULL market_resolved 2,155 2,155 0 69 FULL new_market 1,460 1,460 0 4 FULL price_change 108,153,373 108,150,455 2,918 3,316 FULL tick_size_change 5,464 5,464 0 122 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,792,712 10,367,577 4ms 10ms 113ms 3.3s 0 transport_latency_assumed best_bid_ask e 12,799,834 136,278 41ms 50ms 173ms 4.8s 0 transport_latency_assumed best_bid_ask f 12,140,845 32,914 47ms 60ms 206ms 5.0s 0 transport_latency_assumed best_bid_ask g 12,179,029 3,275 82ms 103ms 353ms 30.5s 0 transport_latency_assumed best_bid_ask h 12,800,445 2,261,969 18ms 29ms 165ms 39.5s 0 transport_latency_assumed book c 1,670,170 1,655,873 25.2min 20.3h 32.3d 103.1d 0 book_staleness book e 112,231 3,898 44ms 185ms 4.8h 84.5d 0 book_staleness book f 507,793 112,594 8.4min 16.7h 28.4d 103.1d 0 book_staleness book g 525,510 56,239 8.9min 16.7h 28.4d 103.1d 0 book_staleness book h 109,930 19,469 21ms 68ms 5.4min 38.3d 0 book_staleness last_trade_price c 44,532 41,990 10ms 47ms 240ms 5.0s 0 transport_latency_assumed last_trade_price e 51,674 580 49ms 134ms 1.2s 5.0s 0 transport_latency_assumed last_trade_price f 49,846 176 56ms 146ms 1.5s 5.0s 0 transport_latency_assumed last_trade_price g 49,555 102 94ms 201ms 2.0s 30.0s 0 transport_latency_assumed last_trade_price h 51,647 8,908 24ms 72ms 407ms 30.3s 0 transport_latency_assumed market_resolved c 1,996 1,962 4ms 4.8min 9.2min 9.8min 0 transport_latency_assumed market_resolved e 1,872 16 54ms 125ms 333ms 53.0s 0 transport_latency_assumed market_resolved f 1,872 12 65ms 132ms 454ms 4.9min 0 transport_latency_assumed market_resolved g 1,872 2 93ms 251ms 1.0s 5.2min 0 transport_latency_assumed market_resolved h 1,872 163 25ms 59ms 281ms 51.7s 0 transport_latency_assumed new_market c 1,090 709 86ms 4.8min 6.2min 6.3min 0 transport_latency_assumed new_market e 971 171 144ms 12.5s 1.7min 2.6min 0 transport_latency_assumed new_market f 967 155 143ms 858ms 1.5min 2.5min 0 transport_latency_assumed new_market g 979 84 240ms 11.0s 1.6min 2.5min 0 transport_latency_assumed new_market h 971 341 85ms 514ms 1.6min 2.5min 0 transport_latency_assumed price_change c 91,883,172 88,107,170 4ms 11ms 123ms 3.5s 0 transport_latency_assumed price_change e 108,023,501 1,144,255 42ms 55ms 226ms 4.8s 0 transport_latency_assumed price_change f 102,801,800 296,009 47ms 65ms 268ms 5.0s 0 transport_latency_assumed price_change g 103,048,899 33,502 83ms 111ms 457ms 30.5s 0 transport_latency_assumed price_change h 108,034,944 18,569,519 18ms 32ms 189ms 39.5s 0 transport_latency_assumed tick_size_change c 5,056 4,834 4ms 12ms 185ms 319ms 0 transport_latency_assumed tick_size_change e 5,464 30 41ms 49ms 247ms 615ms 0 transport_latency_assumed tick_size_change f 5,404 10 47ms 56ms 270ms 554ms 0 transport_latency_assumed tick_size_change g 5,384 not meas. 81ms 99ms 524ms 869ms 0 transport_latency_assumed tick_size_change h 5,464 590 18ms 25ms 179ms 506ms 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/01/2026-09-10T01.parquet sha256sum 2026-09-10T01.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.