Hour audit: 2026-08-30T17
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-30T17 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T17:00:00.032972507+00:00 · last event 2026-08-30T17:59:59.470130852+00:00
VOLUME 92,420,855 rows · 1,000,959,739 bytes (954.59 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 92,333,115 · h: 92,278,044 · a: 92,199,967 · e: 91,792,901 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 44,030 (0.05%) · h: 526,720 (0.57%) · a: 58,568 (0.06%) · e: 91,791,537 (99.32%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 92,420,855 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 4cadd800475a4be09cb3fa488af711da90fe943645638ccd810f403b5d5d78cf
the corpus checksum ledger names this file with the same digest
joined 92,422,225 to merged 92,420,855, minus 1,370 (minus 0.0015%)
boundary drops 1,370 · 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-08-30T19:16:23Z as aceh
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 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 for about half an hour, 2026-08-30T17:55Z to 2026-08-30T18:29ZThe 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 7,281,561 94,510,990 0-27 76fd01fb6f7f728ff7a1bd42810f996db0870611e4bf91ab6aaf7eebe0dd1718 book 233,741 23,608,955 28-28 9c9a4b1b8c4533876cff9ae603edcdc114b37e0c849d0f9a765ea2c731736d87 last_trade_price 83,711 4,748,758 29-29 de134cf8b2d8cfce83460fa4e78ac98a3488054e6c7259d918dff48cd2f3319f market_resolved 1,422 223,962 30-30 f057864b4b5f054c70ddfb6f40d4ed74be8a411ed8777a338379970bbfb2a9b8 new_market 4,065 403,151 31-31 a5261b21cdc4bbbc7a3704c53ba1b78531bcacf8f5e50e3ffc9969be0e0ce8fb price_change 84,806,991 876,069,927 32-355 b065d06e1e07eaf5c7e50c3a5285925dfcfe2e856ad8720f20cb2e6a17e84165 tick_size_change 9,364 340,887 356-356 e43201bf6701b43c2e3ec4ae39afdf133c723a66796df5aaac85f43caf8baa83 EVENT MIX count share price_change 84,806,991 91.76% best_bid_ask 7,281,561 7.88% book 233,741 0.25% last_trade_price 83,711 0.09% tick_size_change 9,364 0.01% new_market 4,065 <0.01% market_resolved 1,422 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,281,695 7,281,561 134 114,129 PARTIAL book 233,741 233,741 0 30,343 PARTIAL last_trade_price 83,711 83,711 0 5,076 PARTIAL market_resolved 1,422 1,422 0 1,387 PARTIAL new_market 4,065 4,065 0 2,615 PARTIAL price_change 84,808,227 84,806,991 1,236 149,628 PARTIAL tick_size_change 9,364 9,364 0 2,341 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,270,108 340 38ms 81ms 680ms 26.7s 0 transport_latency_assumed best_bid_ask c 7,279,509 2,055 5ms 10ms 240ms 5.3s 0 transport_latency_assumed best_bid_ask e 7,256,747 7,256,613 44ms 155ms 2.2s 33.9s 0 transport_latency_assumed best_bid_ask h 7,278,054 22,553 13ms 24ms 342ms 46.3s 0 transport_latency_assumed book a 218,592 46,379 117ms 2.0min 14.7d 92.8d 0 book_staleness book c 177,698 3,334 8ms 39ms 5.0s 74.3d 0 book_staleness book e 175,367 175,367 73ms 5.4s 7.1min 2.3d 0 book_staleness book h 176,211 8,661 22ms 144ms 2.4s 35.8d 0 book_staleness last_trade_price a 82,216 4 56ms 2.0s 10.7s 26.5s 0 transport_latency_assumed last_trade_price c 83,671 11 10ms 40ms 263ms 5.4s 0 transport_latency_assumed last_trade_price e 80,654 80,654 64ms 3.6s 15.8s 33.8s 0 transport_latency_assumed last_trade_price h 83,674 3,042 19ms 109ms 823ms 9.7s 0 transport_latency_assumed market_resolved a 1,387 17 40ms 361ms 58.2s 1.0min 0 transport_latency_assumed market_resolved c 1,387 5 5ms 13ms 58.0s 1.0min 0 transport_latency_assumed market_resolved e 1,387 1,387 44ms 402ms 58.3s 1.0min 0 transport_latency_assumed market_resolved h 1,387 13 14ms 65ms 55.9s 58.8s 0 transport_latency_assumed new_market a 2,615 258 257ms 21.7s 36.5s 1.2min 0 transport_latency_assumed new_market c 2,615 319 91ms 23.0s 54.9s 2.8min 0 transport_latency_assumed new_market e 2,615 2,615 129ms 21.4s 41.7s 1.2min 0 transport_latency_assumed new_market h 2,615 873 137ms 23.8s 45.5s 1.7min 0 transport_latency_assumed price_change a 84,615,685 11,570 38ms 114ms 2.7s 26.7s 0 transport_latency_assumed price_change c 84,778,871 38,306 5ms 11ms 242ms 5.4s 0 transport_latency_assumed price_change e 84,266,767 84,265,537 44ms 215ms 6.1s 34.2s 0 transport_latency_assumed price_change h 84,726,739 491,578 13ms 28ms 360ms 46.3s 0 transport_latency_assumed tick_size_change a 9,364 not meas. 38ms 74ms 363ms 683ms 0 transport_latency_assumed tick_size_change c 9,364 not meas. 5ms 8ms 188ms 411ms 0 transport_latency_assumed tick_size_change e 9,364 9,364 45ms 173ms 466ms 6.4s 0 transport_latency_assumed tick_size_change h 9,364 not meas. 13ms 21ms 281ms 1.9s 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-08-30/17/2026-08-30T17.parquet sha256sum 2026-08-30T17.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.