Hour audit: 2026-08-29T19
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-08-29T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T19:00:00.012616497+00:00 · last event 2026-08-29T19:59:59.999972272+00:00
VOLUME 129,078,769 rows · 1,374,540,221 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 128,155,779 · e: 125,326,684 · a: 121,736,311 · c: 116,676,272 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · e: not measured · a: not measured · c: not measured (rows of the merged file that came from it; these partition it)
28 product-machine pairs publish no supplied count, and the figures above do not reconcile to the file's row count, so the split is incomplete by an unrecorded amount
INTEGRITY sha256 2f3d151472b8e1696263bc9ce201bb9b69ef37446f34e516169bad6e51ddb34f
the corpus checksum ledger names this file with the same digest
joined 129,080,713 to merged 129,078,769, minus 1,944 (minus 0.0015%)
boundary drops 1,944 · 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 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
PASS byte ranges tile the file
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
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 10,958,343 124,907,111 0-41 e45c808dc5aeb9663e061d7b17c9d64e771e667fb7f81c2e3e791af5354cd7bf book 1,048,138 70,007,805 42-45 72b56a06ae83fa0bc1d74ac91f4d13d8cae73eb3ef99ed7938d2405483fdcbbe last_trade_price 70,167 4,004,370 46-46 f053c1d463ffa13968af3d7816569d5cf198ccb2bfd375352394c214f21c350d market_resolved 2,089 281,421 47-47 a84026a9b0e561db681d8fe1a6369a33c1c27dcd7612bc9a1c94b297a744c6c7 new_market 4,270 382,186 48-48 9b7d58e23785f6dc75fb8f10c47750691312749f445f3f05501da38814c7e3f7 price_change 116,987,914 1,173,215,496 49-495 a640923fd8281816b5ed295b72fedd6ca6ff36189a705858d80f76c2e039f815 tick_size_change 7,848 276,480 496-496 a09a00c4d78c9f6687cb901b2404f9f7d74217aabde2dbb6b37030fe247fbd18 EVENT MIX count share price_change 116,987,914 90.63% best_bid_ask 10,958,343 8.49% book 1,048,138 0.81% last_trade_price 70,167 0.05% tick_size_change 7,848 <0.01% new_market 4,270 <0.01% market_resolved 2,089 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,958,520 10,958,343 177 78,565 PARTIAL book 1,048,202 1,048,138 64 180,331 PARTIAL last_trade_price 70,168 70,167 1 4,552 PARTIAL market_resolved 2,089 2,089 0 1,720 PARTIAL new_market 4,270 4,270 0 2,383 PARTIAL price_change 116,989,616 116,987,914 1,702 152,442 PARTIAL tick_size_change 7,848 7,848 0 1,962 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 10,322,923 not meas. 39ms 67ms 568ms 24.3s 0 not stated best_bid_ask c 9,941,069 not meas. 4ms 9ms 247ms 3.0s 0 not stated best_bid_ask e 10,754,577 not meas. 45ms 169ms 1.9s 30.7s 0 not stated best_bid_ask h 10,956,853 not meas. 15ms 31ms 407ms 1.3min 0 not stated book a 502,879 not meas. 50.2s 4.0h 25.9d 91.9d 0 not stated book c 855,690 not meas. 1.4min 7.2h 27.3d 91.9d 0 not stated book e 147,579 not meas. 90ms 4.4s 3.6min 1.6d 0 not stated book h 148,249 not meas. 23ms 195ms 3.9s 73.3d 0 not stated last_trade_price a 65,696 not meas. 57ms 1.8s 10.3s 24.4s 0 not stated last_trade_price c 62,936 not meas. 9ms 44ms 288ms 5.0s 0 not stated last_trade_price e 68,755 not meas. 73ms 3.3s 15.1s 30.7s 0 not stated last_trade_price h 70,146 not meas. 21ms 121ms 941ms 39.9s 0 not stated market_resolved a 1,637 not meas. 40ms 259ms 2.0min 2.4min 0 not stated market_resolved c 1,883 not meas. 4ms 5.4min 9.4min 12.1min 0 not stated market_resolved e 1,633 not meas. 46ms 599ms 2.0min 2.5min 0 not stated market_resolved h 1,719 not meas. 16ms 64ms 374ms 34.8s 0 not stated new_market a 2,384 not meas. 149ms 26.0s 1.5min 53.1min 0 not stated new_market c 3,040 not meas. 427ms 6.9min 14.2min 1.0h 0 not stated new_market e 2,383 not meas. 356ms 25.4s 1.3min 43.4min 0 not stated new_market h 2,383 not meas. 221ms 27.5s 41.6s 15.9min 0 not stated price_change a 110,833,448 not meas. 39ms 98ms 1.1s 24.4s 0 not stated price_change c 105,804,690 not meas. 4ms 10ms 257ms 4.3s 0 not stated price_change e 114,344,029 not meas. 46ms 266ms 5.2s 30.8s 0 not stated price_change h 116,968,581 not meas. 15ms 33ms 440ms 1.3min 0 not stated tick_size_change a 7,344 not meas. 38ms 50ms 252ms 481ms 0 not stated tick_size_change c 6,964 not meas. 4ms 8ms 191ms 686ms 0 not stated tick_size_change e 7,728 not meas. 46ms 146ms 601ms 29.1s 0 not stated tick_size_change h 7,848 not meas. 15ms 25ms 241ms 3.9s 0 not stated
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-29/19/2026-08-29T19.parquet sha256sum 2026-08-29T19.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.