Hour audit: 2026-08-29T05
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-29T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T05:00:00.036134334+00:00 · last event 2026-08-29T05:59:59.999902514+00:00
VOLUME 90,630,547 rows · 891,338,220 bytes (850.05 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 90,503,623 · c: 90,486,593 · a: 90,482,205 · e: 90,265,202 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · c: not measured · a: not measured · e: 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 824646ed14b4a72789a50a19cd1af13a020afb1940f604277cc541e371d79a35
the corpus checksum ledger names this file with the same digest
joined 90,632,223 to merged 90,630,547, minus 1,676 (minus 0.0018%)
boundary drops 1,676 · 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 9,201,326 101,345,603 0-35 c13cf5cc368ab7b718f676d8e995a288cafc73d6174ba0f197d91da265409dad book 270,408 28,457,111 36-37 3f6747d41715d6725183491dc39e6389f60af70aaee9182bdc939a2f30b6b6d6 last_trade_price 45,141 2,628,888 38-38 ee0c8e338dbb006df99baaa417ef5aea545277114b6f92b5536901fd75320f0a market_resolved 938 147,073 39-39 a718c299c4bd144f70b7a5d6abf027c9984b7c32433d17f2708e9a1b4e58656d new_market 594 61,889 40-40 7b7e69478893d102b30b17e5e4499fabccca4219d34fb4bd8acc327076676631 price_change 81,109,820 757,573,339 41-350 ff6374117f67d59ea120af17039119d11b2f33e1486f1a58323271ded1ab6037 tick_size_change 2,320 86,040 351-351 ad9be07f6c29c8d799236cf94f72c9bc79017a86d8a6a0f4f5851b8eabda7cf0 EVENT MIX count share price_change 81,109,820 89.50% best_bid_ask 9,201,326 10.15% book 270,408 0.30% last_trade_price 45,141 0.05% tick_size_change 2,320 <0.01% market_resolved 938 <0.01% new_market 594 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,201,518 9,201,326 192 68,457 PARTIAL book 270,828 270,408 420 81,517 PARTIAL last_trade_price 45,143 45,141 2 3,329 PARTIAL market_resolved 938 938 0 911 PARTIAL new_market 594 594 0 403 PARTIAL price_change 81,110,882 81,109,820 1,062 128,566 PARTIAL tick_size_change 2,320 2,320 0 580 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,199,794 not meas. 39ms 44ms 154ms 7.0s 0 not stated best_bid_ask c 9,200,908 not meas. 4ms 6ms 28ms 2.7s 0 not stated best_bid_ask e 9,195,438 not meas. 44ms 70ms 714ms 15.6s 0 not stated best_bid_ask h 9,200,320 not meas. 12ms 15ms 53ms 5.6s 0 not stated book a 138,251 not meas. 129ms 37.1min 20.6d 91.3d 0 not stated book c 137,585 not meas. 8ms 39.6min 20.6d 91.3d 0 not stated book e 134,112 not meas. 261ms 19.5min 20.6d 72.8d 0 not stated book h 155,793 not meas. 42ms 2.6h 20.6d 91.3d 0 not stated last_trade_price a 45,100 not meas. 52ms 857ms 3.9s 7.0s 0 not stated last_trade_price c 45,120 not meas. 9ms 35ms 146ms 4.9s 0 not stated last_trade_price e 44,528 not meas. 66ms 2.7s 9.4s 15.6s 0 not stated last_trade_price h 45,080 not meas. 18ms 80ms 492ms 4.9s 0 not stated market_resolved a 911 not meas. 39ms 184ms 44.4s 1.0min 0 not stated market_resolved c 911 not meas. 4ms 7ms 1.0min 1.0min 0 not stated market_resolved e 911 not meas. 44ms 411ms 46.3s 2.2min 0 not stated market_resolved h 911 not meas. 13ms 55ms 45.4s 48.1s 0 not stated new_market a 403 not meas. 159ms 15.1s 23.7s 1.0min 0 not stated new_market c 403 not meas. 54ms 14.3s 24.9s 1.1min 0 not stated new_market e 403 not meas. 171ms 19.2s 29.7s 1.5min 0 not stated new_market h 403 not meas. 65ms 14.7s 24.2s 1.1min 0 not stated price_change a 81,095,426 not meas. 39ms 46ms 378ms 7.1s 0 not stated price_change c 81,099,346 not meas. 4ms 6ms 34ms 2.8s 0 not stated price_change e 80,887,494 not meas. 44ms 90ms 1.9s 15.6s 0 not stated price_change h 81,098,796 not meas. 13ms 16ms 77ms 6.9s 0 not stated tick_size_change a 2,320 not meas. 39ms 47ms 126ms 306ms 0 not stated tick_size_change c 2,320 not meas. 4ms 7ms 35ms 216ms 0 not stated tick_size_change e 2,316 not meas. 44ms 105ms 213ms 2.7s 0 not stated tick_size_change h 2,320 not meas. 13ms 19ms 62ms 95ms 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/05/2026-08-29T05.parquet sha256sum 2026-08-29T05.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.