Hour audit: 2026-08-29T04
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-29T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T04:00:00.032446303+00:00 · last event 2026-08-29T04:59:59.999997480+00:00
VOLUME 97,162,101 rows · 991,353,447 bytes (945.43 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 96,760,974 · a: 96,748,901 · e: 96,154,060 · h: 92,994,587 (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 8ca8164d613bc98b8020ba34a032fffeb58974f92b3c57146a42f11345a678c8
the corpus checksum ledger names this file with the same digest
joined 97,163,242 to merged 97,162,101, minus 1,141 (minus 0.0012%)
boundary drops 1,141 · 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,587,762 106,842,182 0-36 ef97a4127349a9ae61b991b68ba6054950aceecf529e625641db17d3541f088f book 502,584 54,248,594 37-38 bc2aa264b40d23bf7f9eb57d5c491799b75d136fbd8c7993731d3afc1207a2ed last_trade_price 49,080 2,843,167 39-39 6898cdc73e9dba5689c47e4d4bbb8239d6801d1d98f3f023911aed2f654004ae market_resolved 1,281 208,350 40-40 30f3b86abe9e7fcc26ab832cacb11ee5837d7f7f35f6dc8f69e89d57b91b161a new_market 2,994 314,052 41-41 3a2f28a9d896894e25c5f323d05895960f53c84b45624321ed8b87e4f95fa944 price_change 87,014,956 825,665,117 42-373 5900a28489efbb60efd541e81569c0e00fcbf7c5ee01d5f060ec165f044bce90 tick_size_change 3,444 126,409 374-374 43496edf05ae7e93b593a92621843a0bb9f5dc615db374ffbd85f5caa005795e EVENT MIX count share price_change 87,014,956 89.56% best_bid_ask 9,587,762 9.87% book 502,584 0.52% last_trade_price 49,080 0.05% tick_size_change 3,444 <0.01% new_market 2,994 <0.01% market_resolved 1,281 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,587,843 9,587,762 81 73,530 PARTIAL book 502,596 502,584 12 183,667 PARTIAL last_trade_price 49,082 49,080 2 3,107 PARTIAL market_resolved 1,281 1,281 0 1,252 PARTIAL new_market 2,994 2,994 0 2,075 PARTIAL price_change 87,016,002 87,014,956 1,046 132,158 PARTIAL tick_size_change 3,444 3,444 0 861 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,584,506 not meas. 36ms 49ms 438ms 17.4s 0 not stated best_bid_ask c 9,586,848 not meas. 4ms 6ms 195ms 3.1s 0 not stated best_bid_ask e 9,564,732 not meas. 44ms 116ms 1.6s 41.7s 0 not stated best_bid_ask h 9,213,334 not meas. 12ms 19ms 512ms 49.8s 0 not stated book a 118,076 not meas. 81ms 21.6s 1.0d 91.2d 0 not stated book c 113,546 not meas. 7ms 1.9s 11.6h 72.8d 0 not stated book e 109,996 not meas. 110ms 14.3s 4.4h 37.2d 0 not stated book h 471,040 not meas. 1.3min 7.2h 26.5d 91.3d 0 not stated last_trade_price a 48,874 not meas. 57ms 1.4s 6.7s 17.4s 0 not stated last_trade_price c 49,021 not meas. 9ms 43ms 271ms 5.1s 0 not stated last_trade_price e 46,334 not meas. 74ms 4.3s 20.3s 41.6s 0 not stated last_trade_price h 46,179 not meas. 18ms 148ms 1.0s 47.1s 0 not stated market_resolved a 1,252 not meas. 38ms 236ms 652ms 1.2s 0 not stated market_resolved c 1,252 not meas. 4ms 9ms 194ms 394ms 0 not stated market_resolved e 1,251 not meas. 44ms 270ms 1.5s 20.6s 0 not stated market_resolved h 1,187 not meas. 13ms 64ms 662ms 6.0min 0 not stated new_market a 2,075 not meas. 245ms 27.9s 46.0s 1.0min 0 not stated new_market c 2,075 not meas. 121ms 28.6s 45.3s 1.1min 0 not stated new_market e 2,075 not meas. 211ms 28.1s 45.5s 1.3min 0 not stated new_market h 2,107 not meas. 176ms 30.6s 2.0min 5.5min 0 not stated price_change a 86,990,674 not meas. 37ms 69ms 887ms 17.5s 0 not stated price_change c 87,004,788 not meas. 4ms 7ms 215ms 3.5s 0 not stated price_change e 86,426,228 not meas. 44ms 151ms 5.0s 41.7s 0 not stated price_change h 83,257,348 not meas. 12ms 22ms 551ms 49.8s 0 not stated tick_size_change a 3,444 not meas. 37ms 42ms 146ms 390ms 0 not stated tick_size_change c 3,444 not meas. 4ms 6ms 30ms 117ms 0 not stated tick_size_change e 3,444 not meas. 44ms 118ms 1.7s 18.4s 0 not stated tick_size_change h 3,392 not meas. 12ms 15ms 61ms 3.6s 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/04/2026-08-29T04.parquet sha256sum 2026-08-29T04.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.