Hour audit: 2026-09-03T20
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-03T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T20:00:00.001713197+00:00 · last event 2026-09-03T20:59:59.999887299+00:00
VOLUME 26,126,479 rows · 269,840,410 bytes (257.34 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 19,282,211 · c: 19,022,731 · e: 16,071,791 · b: 13,938,984 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,197,338 (23.72%) · c: 3,169,523 (12.13%) · e: 16,071,655 (61.51%) · b: 687,963 (2.63%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 26,126,479 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 af7c72101852f65c8f4edf4c9426a4cbd7577e3bafa4aa1fc5547a5b47f98f07
the corpus checksum ledger names this file with the same digest
joined 26,126,765 to merged 26,126,479, minus 286 (minus 0.0011%)
boundary drops 286 · 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-03T21:39: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 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 3,908,212 49,321,598 0-14 9aa2151fa387a9d71751fcedf5c140fa69bc9895416cc5356087d2973f3c3f83 book 142,792 12,806,204 15-15 23ca7e4b657a0544b60bb6ba2688b817c00415df12f097549f29c166e9ae4711 last_trade_price 27,087 1,611,077 16-16 a5e8506fee6b8302b9dbf202a0e208d0fc90b7d6e0dca70b72cb3a98089d59cc market_resolved 1,661 270,048 17-17 3dac2f170adf0aa5468df924c23b389efe015ea6f528f104d349acff57907453 new_market 2,667 295,673 18-18 9015fcf0712b11dfda473768a9e322010747337f912eeddd8f2ae41077cca83f price_change 22,039,332 205,053,638 19-103 aaf1e72525eb7ef9b95c27eb5b4929e32f0e45f81e9de75bb81ce3ff122714d2 tick_size_change 4,728 172,235 104-104 85a9cf75309b10e8a2a807173e69a0be10b1ee7d82f67f7a574cc696118d96a3 EVENT MIX count share price_change 22,039,332 84.36% best_bid_ask 3,908,212 14.96% book 142,792 0.55% last_trade_price 27,087 0.10% tick_size_change 4,728 0.02% new_market 2,667 0.01% market_resolved 1,661 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 3,908,220 3,908,212 8 3,036 FULL book 142,936 142,792 144 34,922 FULL last_trade_price 27,087 27,087 0 108 FULL market_resolved 1,661 1,661 0 52 FULL new_market 2,667 2,667 0 0 FULL price_change 22,039,466 22,039,332 134 88,469 FULL tick_size_change 4,728 4,728 0 58 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 3,796,905 not meas. 50ms 172ms 6.9s 34.4s 0 transport_latency_assumed best_bid_ask c 3,907,830 2,796 4ms 10ms 470ms 11.3s 0 transport_latency_assumed best_bid_ask e 3,877,917 3,877,911 42ms 206ms 9.2s 44.9s 0 transport_latency_assumed best_bid_ask h 3,809,960 27,505 18ms 34ms 486ms 47.0s 0 transport_latency_assumed book b 94,575 35,366 3.4s 3.3h 23.9d 96.9d 0 book_staleness book c 67,156 8,683 9ms 31.0s 1.1d 78.4d 0 book_staleness book e 64,370 64,370 195ms 2.6min 8.6h 13.1d 0 book_staleness book h 85,995 34,373 136ms 1.0h 23.1d 95.3d 0 book_staleness last_trade_price b 25,219 1 100ms 4.7s 14.6s 32.0s 0 transport_latency_assumed last_trade_price c 27,078 481 11ms 82ms 947ms 6.6s 0 transport_latency_assumed last_trade_price e 24,773 24,773 96ms 5.0s 16.4s 40.0s 0 transport_latency_assumed last_trade_price h 25,276 1,832 30ms 432ms 6.4s 16.9s 0 transport_latency_assumed market_resolved b 1,615 8 52ms 207ms 1.3s 2.1min 0 transport_latency_assumed market_resolved c 1,645 3 4ms 7ms 168ms 1.5s 0 transport_latency_assumed market_resolved e 1,645 1,645 43ms 178ms 883ms 59.0s 0 transport_latency_assumed market_resolved h 1,623 5 19ms 58ms 421ms 2.2min 0 transport_latency_assumed new_market b 1,916 184 338ms 14.6s 2.6min 2.6min 0 transport_latency_assumed new_market c 1,916 90 74ms 700ms 1.7min 2.7min 0 transport_latency_assumed new_market e 1,916 1,916 322ms 1.1min 2.2min 2.7min 0 transport_latency_assumed new_market h 1,916 477 141ms 440ms 2.1min 2.2min 0 transport_latency_assumed price_change b 10,014,166 652,404 52ms 1.1s 12.6s 34.7s 0 transport_latency_assumed price_change c 15,012,378 3,157,470 5ms 15ms 592ms 12.1s 0 transport_latency_assumed price_change e 12,096,442 12,096,312 43ms 914ms 12.5s 42.5s 0 transport_latency_assumed price_change h 15,352,809 6,133,146 18ms 59ms 1.6s 47.0s 0 transport_latency_assumed tick_size_change b 4,588 not meas. 50ms 67ms 1.4s 2.6s 0 transport_latency_assumed tick_size_change c 4,728 not meas. 4ms 7ms 383ms 2.4s 0 transport_latency_assumed tick_size_change e 4,728 4,728 44ms 200ms 2.4s 5.4s 0 transport_latency_assumed tick_size_change h 4,632 not meas. 18ms 23ms 271ms 2.2s 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/20/2026-09-03T20.parquet sha256sum 2026-09-03T20.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.