Hour audit: 2026-09-03T18
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-03T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T18:00:00.036335439+00:00 · last event 2026-09-03T18:59:59.127210022+00:00
VOLUME 471,243 rows · 33,391,671 bytes (31.84 MiB) · 7 products, 1 holding no rows
WITNESSES bceh — 4 machines contributed rows
captured h: 272,376 · c: 263,387 · e: 186,508 · b: 70,502 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 172,238 (36.55%) · c: 105,047 (22.29%) · e: 186,498 (39.58%) · b: 7,460 (1.58%) (rows of the merged file that came from it; these partition it)
7 product-machine pairs publish no supplied count; the figures above still sum to the file's 471,243 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 1fa332d7128aa6ee41b6ee227af5cc53373412a830f427bf0468948966995086
the corpus checksum ledger names this file with the same digest
joined 471,269 to merged 471,243, minus 26 (minus 0.0055%)
boundary drops 26 · 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-03T19:36:17Z 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 7/8 pass, 1 not evaluated
PASS all products present
PASS row counts reconcile
SKIPPED the byte ranges could not be checked
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: Venue paused trading, then twice more in cancel-only mode, 2026-09-03T17:06Z to 2026-09-03T21:35ZThe 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,238 511,648 0-0 4348fff49186fc1d7923a0f57bcd936f832d5280d3afcd158b16487b3b00d839 book 260,239 29,190,419 1-1 9942a2a16f9a7e9a61341474eca0666afa16749e67a87aa431adb2a5f93320e5 last_trade_price 0 not meas. 2-1 not published market_resolved 794 129,933 2-2 6398c3dda523d63befc26628a5abaa473755fef767933e503de523293a9da00c new_market 2,912 300,282 3-3 f28ccd8fbc215953dee10f4378ce67c5ed2dafdae6d4dd29b7ac2b10c833c08e price_change 197,056 3,236,849 4-4 c34bf729b3b8ab15e8e25daf12af863a74177cb75b9458b26eeef7af06e64c1c tick_size_change 4 2,031 5-5 c6025d203ae62d0d7fdc8d408c53c87e1d6e481952a7649d7d0cf7d53bef9f7e EVENT MIX count share book 260,239 55.22% price_change 197,056 41.82% best_bid_ask 10,238 2.17% new_market 2,912 0.62% market_resolved 794 0.17% tick_size_change 4 <0.01% last_trade_price 0 0.00% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,238 10,238 0 24 FULL book 260,265 260,239 26 127,608 FULL last_trade_price 0 0 0 0 NO-SOURCE market_resolved 794 794 0 2 FULL new_market 2,912 2,912 0 0 FULL price_change 197,056 197,056 0 10,178 FULL tick_size_change 4 4 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,232 not meas. 53ms 228ms 649ms 1.4s 0 transport_latency_assumed best_bid_ask c 10,170 not meas. 6ms 24ms 342ms 723ms 0 transport_latency_assumed best_bid_ask e 10,202 10,202 45ms 593ms 2.5s 4.0s 0 transport_latency_assumed best_bid_ask h 10,220 36 20ms 68ms 390ms 5.8s 0 transport_latency_assumed book b 15,201 4,433 1.1h 4.6h 26.2d 96.8d 0 book_staleness book c 133,746 62,449 1.2h 6.6h 32.3d 96.8d 0 book_staleness book e 90,047 90,037 1.2h 7.4h 32.3d 96.8d 0 book_staleness book h 137,489 103,320 1.2h 8.6h 32.3d 96.8d 0 book_staleness market_resolved b 792 not meas. 51ms 142ms 455ms 52.4s 0 transport_latency_assumed market_resolved c 790 2 6ms 8ms 236ms 1.7min 0 transport_latency_assumed market_resolved e 792 792 40ms 120ms 503ms 44.5s 0 transport_latency_assumed market_resolved h 792 not meas. 19ms 41ms 228ms 45.0s 0 transport_latency_assumed new_market b 1,975 265 258ms 14.2s 24.8s 56.0s 0 transport_latency_assumed new_market c 1,975 132 85ms 13.1s 25.0s 1.1min 0 transport_latency_assumed new_market e 1,975 1,975 237ms 15.5s 27.6s 1.1min 0 transport_latency_assumed new_market h 1,975 540 157ms 13.3s 22.3s 1.0min 0 transport_latency_assumed price_change b 42,298 2,762 132ms 403ms 952ms 1.2s 0 transport_latency_assumed price_change c 116,702 42,464 8ms 36ms 283ms 2.1s 0 transport_latency_assumed price_change e 83,488 83,488 76ms 851ms 2.7s 4.2s 0 transport_latency_assumed price_change h 121,896 68,342 39ms 142ms 386ms 6.1s 0 transport_latency_assumed tick_size_change b 4 not meas. 52ms 52ms 52ms 52ms 0 transport_latency_assumed tick_size_change c 4 not meas. 6ms 6ms 6ms 6ms 0 transport_latency_assumed tick_size_change e 4 4 40ms 40ms 40ms 40ms 0 transport_latency_assumed tick_size_change h 4 not meas. 22ms 22ms 22ms 22ms 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-03/18/2026-09-03T18.parquet sha256sum 2026-09-03T18.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.