Hour audit: 2026-08-29T08
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-29T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T08:00:00.036381631+00:00 · last event 2026-08-29T08:59:59.999984739+00:00
VOLUME 81,470,762 rows · 820,752,299 bytes (782.73 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 81,295,292 · h: 81,294,540 · a: 81,293,655 · e: 81,187,463 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: 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 5fa7cb3be4a2a751f5215fda05e8870afcbd7b5c9fa084670950984e1de66468
the corpus checksum ledger names this file with the same digest
joined 81,472,451 to merged 81,470,762, minus 1,689 (minus 0.0021%)
boundary drops 1,689 · 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 5,886,872 70,252,581 0-22 db73f9f8833bbe51e61e2329425db985726a1fe3c8694993154fea29dcf512e2 book 320,825 32,903,307 23-24 b205db1540730d4573a986527b4939290ea0359ece943d3937d3fc87a136ec93 last_trade_price 54,090 3,123,218 25-25 5566e866b48d158d3a21e156d15ca7a52617b19edd98e63350db7ec052a1af4f market_resolved 563 86,444 26-26 9909b208b532d83dccc2ae1686b6ad3e2e68885b8cbdcaa4cdda919f80643685 new_market 862 87,387 27-27 e36e61c6d011bc89db2589503fe7312255e08eba8853278e105084525595b67a price_change 75,205,430 713,288,296 28-314 32c024b036b2d7e950e67b10a358c0d91a03288af0901ec7ecb6338a38fda766 tick_size_change 2,120 78,429 315-315 e335f3fc8914d3f5f64acebb094441219a61597a6c99aff193f7e1fc1c814147 EVENT MIX count share price_change 75,205,430 92.31% best_bid_ask 5,886,872 7.23% book 320,825 0.39% last_trade_price 54,090 0.07% tick_size_change 2,120 <0.01% new_market 862 <0.01% market_resolved 563 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 5,887,045 5,886,872 173 73,377 PARTIAL book 320,847 320,825 22 92,187 PARTIAL last_trade_price 54,090 54,090 0 3,832 PARTIAL market_resolved 563 563 0 539 PARTIAL new_market 862 862 0 573 PARTIAL price_change 75,206,924 75,205,430 1,494 138,313 PARTIAL tick_size_change 2,120 2,120 0 530 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 5,884,675 not meas. 38ms 45ms 313ms 11.5s 0 not stated best_bid_ask c 5,886,080 not meas. 4ms 7ms 58ms 1.6s 0 not stated best_bid_ask e 5,879,991 not meas. 45ms 89ms 1.0s 19.3s 0 not stated best_bid_ask h 5,886,160 not meas. 12ms 16ms 104ms 44.1s 0 not stated book a 180,780 not meas. 216ms 26.9min 20.8d 91.4d 0 not stated book c 164,567 not meas. 9ms 11.1min 20.8d 91.4d 0 not stated book e 177,541 not meas. 560ms 17.7min 20.8d 91.4d 0 not stated book h 156,896 not meas. 26ms 7.0min 20.7d 91.4d 0 not stated last_trade_price a 53,870 not meas. 51ms 1.0s 5.7s 11.5s 0 not stated last_trade_price c 54,051 not meas. 9ms 36ms 175ms 4.9s 0 not stated last_trade_price e 52,719 not meas. 65ms 2.4s 14.6s 19.2s 0 not stated last_trade_price h 54,042 not meas. 17ms 84ms 642ms 7.0s 0 not stated market_resolved a 539 not meas. 39ms 275ms 466ms 604ms 0 not stated market_resolved c 539 not meas. 4ms 8ms 32ms 170ms 0 not stated market_resolved e 539 not meas. 45ms 291ms 986ms 1.2s 0 not stated market_resolved h 539 not meas. 12ms 66ms 102ms 239ms 0 not stated new_market a 573 not meas. 186ms 15.4s 28.4s 1.1min 0 not stated new_market c 573 not meas. 76ms 12.9s 28.3s 1.0min 0 not stated new_market e 573 not meas. 197ms 17.2s 27.7s 1.1min 0 not stated new_market h 573 not meas. 135ms 14.2s 34.1s 1.1min 0 not stated price_change a 75,171,098 not meas. 38ms 49ms 580ms 11.6s 0 not stated price_change c 75,187,362 not meas. 4ms 7ms 72ms 1.8s 0 not stated price_change e 75,073,980 not meas. 45ms 104ms 1.9s 19.3s 0 not stated price_change h 75,194,210 not meas. 12ms 17ms 141ms 44.1s 0 not stated tick_size_change a 2,120 not meas. 38ms 45ms 174ms 356ms 0 not stated tick_size_change c 2,120 not meas. 4ms 6ms 226ms 670ms 0 not stated tick_size_change e 2,120 not meas. 45ms 125ms 1.4s 1.8s 0 not stated tick_size_change h 2,120 not meas. 12ms 16ms 138ms 1.0s 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/08/2026-08-29T08.parquet sha256sum 2026-08-29T08.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.