Hour audit: 2026-08-29T09
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-29T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T09:00:00.035191809+00:00 · last event 2026-08-29T09:59:59.999971332+00:00
VOLUME 92,116,365 rows · 969,764,125 bytes (924.84 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 91,673,480 · a: 91,615,367 · e: 91,551,069 · h: 88,145,963 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · a: not measured · e: not measured · h: 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 6be05d268863857596634332e80c4509f144bdd73203f72fda46b18558235095
the corpus checksum ledger names this file with the same digest
joined 92,117,431 to merged 92,116,365, minus 1,066 (minus 0.0012%)
boundary drops 1,066 · 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 6,429,346 77,205,895 0-24 60411cee4eb93ac57e0580a566fe156e4d2ac08ee0b9eb9e89023c09391d2b2f book 582,127 56,592,631 25-27 a56c2b896db89002a0292df7a3627ac33b6422838bbe537448a42524718f94b0 last_trade_price 59,901 3,417,503 28-28 e33529c8965d0ac72be6bf33efc02215d3df0233b2d65aa534ac7b054a4305d1 market_resolved 540 79,752 29-29 dc9c08be8b97814362a3779579f2c3f14a8a6bf11adac4403604c31fe2e0a7e2 new_market 835 90,222 30-30 d7546a77ca9b380aae8e6431085d4f2a3ef86e956634b7e9537434db65d16ac7 price_change 85,040,872 831,223,729 31-355 285ce503b5bd848aacfb0621ede233b50f78329b8b55933181c7da2e7055cfb2 tick_size_change 2,744 100,782 356-356 388eb6ec8be85c0a154b10dd3370db6302c4ad8bfe54f844b8f459966a9fe1e1 EVENT MIX count share price_change 85,040,872 92.32% best_bid_ask 6,429,346 6.98% book 582,127 0.63% last_trade_price 59,901 0.07% tick_size_change 2,744 <0.01% new_market 835 <0.01% market_resolved 540 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,429,416 6,429,346 70 73,585 PARTIAL book 582,133 582,127 6 183,220 PARTIAL last_trade_price 59,901 59,901 0 3,793 PARTIAL market_resolved 540 540 0 492 PARTIAL new_market 835 835 0 594 PARTIAL price_change 85,041,862 85,040,872 990 140,016 PARTIAL tick_size_change 2,744 2,744 0 686 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,425,922 not meas. 39ms 48ms 284ms 17.7s 0 not stated best_bid_ask c 6,428,858 not meas. 4ms 7ms 59ms 2.0s 0 not stated best_bid_ask e 6,422,604 not meas. 40ms 92ms 959ms 19.7s 0 not stated best_bid_ask h 6,149,298 not meas. 12ms 23ms 106ms 19.6s 0 not stated book a 162,157 not meas. 104ms 3.8min 17.6d 91.5d 0 not stated book c 153,145 not meas. 8ms 2.0min 6.8d 91.5d 0 not stated book e 149,248 not meas. 100ms 2.4min 6.8d 73.0d 0 not stated book h 512,272 not meas. 1.1min 4.8h 25.8d 91.5d 0 not stated last_trade_price a 59,330 not meas. 56ms 1.2s 10.3s 17.7s 0 not stated last_trade_price c 59,879 not meas. 9ms 41ms 226ms 4.8s 0 not stated last_trade_price e 58,793 not meas. 63ms 2.8s 12.3s 19.4s 0 not stated last_trade_price h 57,533 not meas. 18ms 111ms 911ms 19.6s 0 not stated market_resolved a 492 not meas. 42ms 40.9s 1.0min 1.0min 0 not stated market_resolved c 492 not meas. 4ms 20ms 56.0s 1.0min 0 not stated market_resolved e 492 not meas. 42ms 40.9s 1.0min 1.0min 0 not stated market_resolved h 467 not meas. 16ms 41.2s 1.0min 5.3min 0 not stated new_market a 594 not meas. 181ms 18.0s 38.2s 1.2min 0 not stated new_market c 594 not meas. 60ms 13.9s 40.1s 57.6s 0 not stated new_market e 594 not meas. 177ms 12.4s 26.7s 1.1min 0 not stated new_market h 594 not meas. 92ms 14.3s 45.6s 3.8min 0 not stated price_change a 84,964,128 not meas. 40ms 57ms 671ms 17.8s 0 not stated price_change c 85,027,768 not meas. 4ms 8ms 88ms 2.0s 0 not stated price_change e 84,916,594 not meas. 41ms 113ms 2.3s 19.8s 0 not stated price_change h 81,423,175 not meas. 12ms 25ms 165ms 20.3s 0 not stated tick_size_change a 2,744 not meas. 39ms 49ms 148ms 453ms 0 not stated tick_size_change c 2,744 not meas. 4ms 8ms 60ms 160ms 0 not stated tick_size_change e 2,744 not meas. 40ms 72ms 203ms 8.7s 0 not stated tick_size_change h 2,624 not meas. 12ms 19ms 88ms 237ms 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/09/2026-08-29T09.parquet sha256sum 2026-08-29T09.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.