Hour audit: 2026-09-10T17
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-10T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T17:00:00.000932786+00:00 · last event 2026-09-10T17:59:59.999945519+00:00
VOLUME 116,315,034 rows · 1,249,259,178 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 114,592,319 · g: 114,584,856 · h: 114,544,247 · e: 114,483,988 · c: 96,490,066 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 379,570 (0.33%) · g: 50,366 (0.04%) · h: 24,801,468 (21.32%) · e: 1,296,282 (1.11%) · c: 89,787,348 (77.19%) (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 116,315,034 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 04aa3cac2ca4bcd9eaba6225a61f9b4569b89397c4e035a52a5c86246a67f8c8
the corpus checksum ledger names this file with the same digest
joined 116,318,916 to merged 116,315,034, minus 3,882 (minus 0.0033%)
boundary drops 3,882 · 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:02:25Z 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,949,383 123,559,751 0-41 ff9f37d56d0879ed3c70c6e89bf117d8ce06205f1a753c1d91cd7b20b108be90 book 1,738,359 85,544,637 42-48 e848e86536b87c58af61c59e4d4b3c2d0430ca73bf716058a6330d3efa22712d last_trade_price 69,272 3,883,862 49-49 cb501b213f289e02885525808d418a3aae0e66167b742a205e4ce2f4927994cc market_resolved 1,578 166,412 50-50 3a1eaca95fd20f8b643d453b0e02d928ecfd7f3cd592f8faa1e1781658b257d2 new_market 1,030 99,295 51-51 4286b3e02656622736081d7d141b69040948f1631aca331945864fd583e57978 price_change 103,552,088 1,034,558,765 52-447 6c11bffadf004f8c2141121e8a751ee4f7180ab07a654cd49777b01ad24160cc tick_size_change 3,324 121,900 448-448 dae55e5de0dece43c3f49e74d9a64c3921cc8d21ff39ccec7fab24824beceb79 EVENT MIX count share price_change 103,552,088 89.03% best_bid_ask 10,949,383 9.41% book 1,738,359 1.49% last_trade_price 69,272 0.06% tick_size_change 3,324 <0.01% market_resolved 1,578 <0.01% new_market 1,030 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,949,655 10,949,383 272 2,575 FULL book 1,738,421 1,738,359 62 194,723 FULL last_trade_price 69,274 69,272 2 314 FULL market_resolved 1,578 1,578 0 48 FULL new_market 1,030 1,030 0 0 FULL price_change 103,555,634 103,552,088 3,546 1,815 FULL tick_size_change 3,324 3,324 0 122 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,058,736 8,434,136 6ms 17ms 123ms 6.9s 0 transport_latency_assumed best_bid_ask e 10,942,478 117,587 39ms 48ms 176ms 14.4s 0 transport_latency_assumed best_bid_ask f 10,947,124 28,505 46ms 57ms 189ms 3.4s 0 transport_latency_assumed best_bid_ask g 10,945,766 2,383 79ms 98ms 311ms 10.3s 0 transport_latency_assumed best_bid_ask h 10,945,449 2,366,772 18ms 29ms 129ms 14.6s 0 transport_latency_assumed book c 1,700,944 1,689,442 25.3min 1.3d 32.1d 103.8d 0 book_staleness book e 146,853 5,732 42ms 250ms 13.9min 38.0d 0 book_staleness book f 146,579 3,193 49ms 200ms 4.0min 85.3d 0 book_staleness book g 156,606 5,277 89ms 1.7s 17.9h 85.3d 0 book_staleness book h 147,366 34,715 23ms 86ms 5.9min 37.8d 0 book_staleness last_trade_price c 55,721 51,437 12ms 53ms 268ms 5.0s 0 transport_latency_assumed last_trade_price e 68,653 1,107 51ms 200ms 2.5s 14.4s 0 transport_latency_assumed last_trade_price f 69,080 774 58ms 184ms 1.1s 5.1s 0 transport_latency_assumed last_trade_price g 69,038 211 96ms 298ms 3.6s 9.2s 0 transport_latency_assumed last_trade_price h 68,830 15,743 25ms 85ms 625ms 12.2s 0 transport_latency_assumed market_resolved c 1,393 1,340 11ms 15.2min 17.7min 18.8min 0 transport_latency_assumed market_resolved e 989 18 40ms 121ms 45.8s 57.3s 0 transport_latency_assumed market_resolved f 993 2 47ms 162ms 45.8s 57.3s 0 transport_latency_assumed market_resolved g 993 not meas. 81ms 238ms 651ms 964ms 0 transport_latency_assumed market_resolved h 991 218 19ms 59ms 47.1s 58.7s 0 transport_latency_assumed new_market c 783 489 133ms 8.5min 15.3min 15.4min 0 transport_latency_assumed new_market e 620 97 160ms 11.5s 32.2s 58.6s 0 transport_latency_assumed new_market f 620 127 141ms 12.1s 22.8s 1.3min 0 transport_latency_assumed new_market g 620 65 289ms 13.6s 41.9s 1.1min 0 transport_latency_assumed new_market h 620 252 114ms 14.5s 45.9s 1.0min 0 transport_latency_assumed price_change c 85,669,633 79,607,787 6ms 18ms 126ms 8.5s 0 transport_latency_assumed price_change e 103,321,091 1,171,736 39ms 54ms 300ms 14.4s 0 transport_latency_assumed price_change f 103,424,599 346,962 46ms 64ms 257ms 3.9s 0 transport_latency_assumed price_change g 103,408,509 42,430 79ms 111ms 469ms 12.5s 0 transport_latency_assumed price_change h 103,377,667 22,383,173 19ms 32ms 158ms 14.6s 0 transport_latency_assumed tick_size_change c 2,856 2,717 6ms 11ms 102ms 170ms 0 transport_latency_assumed tick_size_change e 3,304 5 39ms 44ms 1.3s 1.4s 0 transport_latency_assumed tick_size_change f 3,324 7 45ms 50ms 110ms 201ms 0 transport_latency_assumed tick_size_change g 3,324 not meas. 78ms 92ms 213ms 2.3s 0 transport_latency_assumed tick_size_change h 3,324 595 19ms 24ms 65ms 660ms 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/17/2026-09-10T17.parquet sha256sum 2026-09-10T17.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.