Hour audit: 2026-09-08T23
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-08T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T23:00:00.000083587+00:00 · last event 2026-09-08T23:59:59.999805341+00:00
VOLUME 87,040,564 rows · 886,251,176 bytes (845.19 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 86,926,425 · c: 86,658,241 · h: 86,559,248 · g: 86,501,074 · e: 86,493,170 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 543,354 (0.62%) · c: 83,136,772 (95.51%) · h: 2,858,037 (3.28%) · g: 36,206 (0.04%) · e: 466,195 (0.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 87,040,564 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d5b462e26b7cd911e8fb84dbd8a9e914cc5c0d875a5c3790fd55b0b633103323
the corpus checksum ledger names this file with the same digest
joined 87,043,636 to merged 87,040,564, minus 3,072 (minus 0.0035%)
boundary drops 3,072 · 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-09T00:53:43Z 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 an incident recorded by the venue intersects this hour: Perpetuals maintenance that overran, on a market this archive does not record, 2026-09-08T22:02Z to 2026-09-09T00:38ZThe 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 6,812,495 78,302,064 0-25 ae1c21ccdd914a901a41939915eeb9222662dcd48bfc9ae91a90843746a51722 book 500,410 38,771,996 26-27 227ebbc8811930fae09b2df3f72162586e7f60e71a508ecad28aafada613cec5 last_trade_price 66,362 3,620,347 28-28 f7a6a78c9c99bdf4fb7b6def2470bddf294335a792050e7c8e24eefe8f2f16bd market_resolved 1,506 243,279 29-29 536a8133135a9868a6ad8fb7ccf6ad330f0d4194b06aa031cfab1952d0617ec8 new_market 4,058 405,058 30-30 898e82611cd1fb7ac096a2126d705c5ed4184947d96b7a3e813eba8d44ce7e4b price_change 79,653,257 763,825,246 31-334 06ced2412794d930b318d57b96227d90d4ec432f89fdad6e79d6a01f0d8ba1e1 tick_size_change 2,476 91,058 335-335 70e9459172c983c15709476c3648b7010bd19aacdaada60abbc9bc5b32a1e2fc EVENT MIX count share price_change 79,653,257 91.51% best_bid_ask 6,812,495 7.83% book 500,410 0.57% last_trade_price 66,362 0.08% new_market 4,058 <0.01% tick_size_change 2,476 <0.01% market_resolved 1,506 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,812,619 6,812,495 124 320 FULL book 500,416 500,410 6 104,404 FULL last_trade_price 66,362 66,362 0 0 FULL market_resolved 1,506 1,506 0 1 FULL new_market 4,058 4,058 0 0 FULL price_change 79,656,199 79,653,257 2,942 353 FULL tick_size_change 2,476 2,476 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,811,153 6,540,575 4ms 9ms 156ms 3.7s 0 transport_latency_assumed best_bid_ask e 6,807,166 39,166 39ms 51ms 263ms 12.5s 0 transport_latency_assumed best_bid_ask f 6,806,225 16,606 46ms 60ms 269ms 13.4s 0 transport_latency_assumed best_bid_ask g 6,801,488 1,512 86ms 129ms 573ms 21.0s 0 transport_latency_assumed best_bid_ask h 6,810,487 214,636 17ms 23ms 363ms 46.6s 0 transport_latency_assumed book c 144,115 134,833 6ms 39ms 4.0s 83.5d 0 book_staleness book e 142,347 3,211 42ms 397ms 11.1s 38.2d 0 book_staleness book f 482,075 337,447 3.4min 17.5h 24.6d 102.1d 0 book_staleness book g 156,367 17,418 94ms 25.2s 1.2d 102.1d 0 book_staleness book h 143,095 7,501 20ms 89ms 3.1s 83.5d 0 book_staleness last_trade_price c 66,307 63,264 9ms 39ms 233ms 5.2s 0 transport_latency_assumed last_trade_price e 65,713 345 45ms 201ms 6.5s 12.6s 0 transport_latency_assumed last_trade_price f 66,020 133 53ms 247ms 8.0s 13.5s 0 transport_latency_assumed last_trade_price g 64,490 11 98ms 373ms 14.4s 21.0s 0 transport_latency_assumed last_trade_price h 66,301 2,609 22ms 65ms 603ms 10.3s 0 transport_latency_assumed market_resolved c 1,457 1,359 4ms 18ms 48.2s 1.0min 0 transport_latency_assumed market_resolved e 1,457 74 40ms 218ms 58.9s 1.0min 0 transport_latency_assumed market_resolved f 1,456 7 47ms 289ms 58.7s 1.0min 0 transport_latency_assumed market_resolved g 1,457 not meas. 88ms 403ms 46.9s 1.0min 0 transport_latency_assumed market_resolved h 1,457 66 17ms 96ms 46.2s 1.0min 0 transport_latency_assumed new_market c 2,613 1,395 85ms 1.1min 3.3min 3.9min 0 transport_latency_assumed new_market e 2,613 620 135ms 58.6s 3.4min 9.5min 0 transport_latency_assumed new_market f 2,613 556 149ms 1.4min 3.5min 17.8min 0 transport_latency_assumed new_market g 2,613 322 237ms 1.3min 3.6min 9.6min 0 transport_latency_assumed new_market h 2,613 1,165 105ms 1.1min 3.3min 9.5min 0 transport_latency_assumed price_change c 79,630,120 76,392,958 4ms 10ms 158ms 5.2s 0 transport_latency_assumed price_change e 79,471,398 422,775 39ms 57ms 343ms 12.5s 0 transport_latency_assumed price_change f 79,565,560 188,597 46ms 65ms 325ms 13.4s 0 transport_latency_assumed price_change g 79,472,183 16,939 87ms 141ms 713ms 21.0s 0 transport_latency_assumed price_change h 79,532,819 2,631,988 17ms 25ms 327ms 48.3s 0 transport_latency_assumed tick_size_change c 2,476 2,388 4ms 8ms 66ms 169ms 0 transport_latency_assumed tick_size_change e 2,476 4 39ms 46ms 153ms 231ms 0 transport_latency_assumed tick_size_change f 2,476 8 46ms 54ms 227ms 454ms 0 transport_latency_assumed tick_size_change g 2,476 4 86ms 106ms 427ms 673ms 0 transport_latency_assumed tick_size_change h 2,476 72 17ms 27ms 109ms 398ms 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-08/23/2026-09-08T23.parquet sha256sum 2026-09-08T23.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.