Hour audit: 2026-09-04T04
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-04T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T04:00:00.000649712+00:00 · last event 2026-09-04T04:59:59.999958280+00:00
VOLUME 94,514,465 rows · 886,748,810 bytes (845.67 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 94,431,228 · h: 69,422,276 · e: 60,776,364 · b: 57,496,948 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 16,990,987 (17.98%) · h: 16,709,993 (17.68%) · e: 60,775,102 (64.30%) · b: 38,383 (0.04%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 94,514,465 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 b25cbb6f33d2188a879fd72a764bc975ea0be359b9f2bdefb16c6fc2f1ba30f2
the corpus checksum ledger names this file with the same digest
joined 94,516,134 to merged 94,514,465, minus 1,669 (minus 0.0018%)
boundary drops 1,669 · 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-04T05:49:22Z as bceh
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 8,773,768 95,229,057 0-33 406dd8cb18e06ea8f2830b0b6a6500f63c11ecb82f8845e0b1630302fd93d2ba book 206,235 20,530,181 34-34 56d10b94372a7bf16bd3ec6fa60fe538dd7bf7ab66992447ac25764ec299344a last_trade_price 56,263 3,084,520 35-35 0b659cdcdf29155412118fd43b84abeaef22a477bbf6e1507ed1906fd2dde8c5 market_resolved 1,014 166,200 36-36 1bdeb777af6d7d927365de2baf162224ccc0958a51f59d504db2f8fa4d2fa605 new_market 2,715 284,764 37-37 202108c512c199cb024307bc351e39644508184851a8469b73f97335af7459f8 price_change 85,472,284 766,295,795 38-364 22b47cb070f93122f7cd57539c244901bba423ae0739d2d9842aac628a915b0e tick_size_change 2,186 78,427 365-365 f28feea87f7d784cf662319899973623a6ef9369b8bcbbedfdff54503d75fede EVENT MIX count share price_change 85,472,284 90.43% best_bid_ask 8,773,768 9.28% book 206,235 0.22% last_trade_price 56,263 0.06% new_market 2,715 <0.01% tick_size_change 2,186 <0.01% market_resolved 1,014 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,773,938 8,773,768 170 162 FULL book 206,241 206,235 6 36,039 FULL last_trade_price 56,264 56,263 1 2 FULL market_resolved 1,014 1,014 0 0 FULL new_market 2,715 2,715 0 0 FULL price_change 85,473,776 85,472,284 1,492 101,290 FULL tick_size_change 2,186 2,186 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,770,353 30 50ms 63ms 321ms 8.1s 0 transport_latency_assumed best_bid_ask c 8,773,114 884 4ms 7ms 129ms 4.1s 0 transport_latency_assumed best_bid_ask e 8,770,622 8,770,483 41ms 55ms 332ms 6.8s 0 transport_latency_assumed best_bid_ask h 8,764,278 2,371 17ms 23ms 399ms 23.9s 0 transport_latency_assumed book b 158,224 37,675 59ms 14.6min 12.6d 78.8d 0 book_staleness book c 141,271 21,902 6ms 1.6min 2.2d 97.3d 0 book_staleness book e 136,286 136,286 44ms 33.2s 2.2d 97.3d 0 book_staleness book h 127,466 10,372 21ms 1.0s 5.6h 78.7d 0 book_staleness last_trade_price b 56,136 1 57ms 162ms 2.0s 8.1s 0 transport_latency_assumed last_trade_price c 56,180 53 9ms 41ms 296ms 5.0s 0 transport_latency_assumed last_trade_price e 56,067 56,066 48ms 172ms 1.7s 6.8s 0 transport_latency_assumed last_trade_price h 55,364 143 23ms 79ms 1.0s 8.4s 0 transport_latency_assumed market_resolved b 1,009 not meas. 52ms 216ms 48.6s 59.3s 0 transport_latency_assumed market_resolved c 1,009 5 4ms 8ms 233ms 57.5s 0 transport_latency_assumed market_resolved e 1,009 1,009 42ms 193ms 47.7s 58.4s 0 transport_latency_assumed market_resolved h 1,009 not meas. 18ms 88ms 47.8s 58.5s 0 transport_latency_assumed new_market b 1,900 157 225ms 17.7s 1.1min 1.7min 0 transport_latency_assumed new_market c 1,900 253 129ms 17.9s 59.3s 1.3min 0 transport_latency_assumed new_market e 1,900 1,900 179ms 18.0s 1.1min 1.3min 0 transport_latency_assumed new_market h 1,900 405 152ms 18.8s 1.1min 2.9min 0 transport_latency_assumed price_change b 48,507,140 520 50ms 69ms 424ms 8.2s 0 transport_latency_assumed price_change c 85,455,568 16,967,890 4ms 7ms 138ms 4.3s 0 transport_latency_assumed price_change e 51,808,294 51,807,172 41ms 72ms 462ms 6.8s 0 transport_latency_assumed price_change h 60,470,073 16,696,702 17ms 25ms 418ms 28.0s 0 transport_latency_assumed tick_size_change b 2,186 not meas. 50ms 62ms 147ms 770ms 0 transport_latency_assumed tick_size_change c 2,186 not meas. 4ms 6ms 54ms 391ms 0 transport_latency_assumed tick_size_change e 2,186 2,186 41ms 46ms 176ms 1.8s 0 transport_latency_assumed tick_size_change h 2,186 not meas. 17ms 20ms 234ms 2.1s 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-04/04/2026-09-04T04.parquet sha256sum 2026-09-04T04.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.