Hour audit: 2026-08-29T15
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-29T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T15:00:00.034759044+00:00 · last event 2026-08-29T15:59:59.999970447+00:00
VOLUME 122,842,608 rows · 1,330,481,816 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 121,399,820 · e: 120,181,343 · c: 111,977,744 · a: 107,221,100 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · e: not measured · c: not measured · a: 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 7db6f83e7cae82372f510e9f91353664dce1d08b099f5cbf3ca4ec6969d47af5
the corpus checksum ledger names this file with the same digest
joined 122,843,852 to merged 122,842,608, minus 1,244 (minus 0.0010%)
boundary drops 1,244 · 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,574,568 122,561,044 0-40 d7e49981f6c94077f26a7a9b685a0162b13f3a183e1086d0bc3cfdd5ff14f71d book 1,587,353 84,639,431 41-47 944e9e94b67d633d11b60d1e93b059ecb02f0b47ea4583c9655c1001e5c68f33 last_trade_price 74,703 4,382,151 48-48 4908e0810b08c355a43a0659ba9d1d860ef110e2e412f5881b98fe7cfa7ff6cc market_resolved 2,520 346,432 49-49 9a18d95165df5accb4c85b268ae75a7bfb1b52b7adcd5f9d5ca4835b1c62feb2 new_market 1,064 102,119 50-50 fe505aa17a21f9122f6c27c7ae01c3914ff289a8357a317bfc59cf4c88a5ab1d price_change 110,590,470 1,116,621,702 51-472 4192b8a6db2b01c28b877438f1f096adc0e78fc6af5963f3151c1f6a191f216f tick_size_change 11,930 430,664 473-473 75fd8f04d7df32017d0e279185d2c4a3a6752f6ee662848783ef8fd0e5f5e108 EVENT MIX count share price_change 110,590,470 90.03% best_bid_ask 10,574,568 8.61% book 1,587,353 1.29% last_trade_price 74,703 0.06% tick_size_change 11,930 <0.01% market_resolved 2,520 <0.01% new_market 1,064 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,574,717 10,574,568 149 89,468 PARTIAL book 1,587,375 1,587,353 22 182,229 PARTIAL last_trade_price 74,704 74,703 1 5,833 PARTIAL market_resolved 2,520 2,520 0 2,155 PARTIAL new_market 1,064 1,064 0 653 PARTIAL price_change 110,591,542 110,590,470 1,072 149,524 PARTIAL tick_size_change 11,930 11,930 0 2,982 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,263,649 not meas. 37ms 46ms 239ms 13.0s 0 not stated best_bid_ask c 9,702,026 not meas. 4ms 8ms 72ms 13.4s 0 not stated best_bid_ask e 10,547,273 not meas. 43ms 104ms 1.5s 21.5s 0 not stated best_bid_ask h 10,573,640 not meas. 13ms 28ms 106ms 10.3s 0 not stated book a 1,221,733 not meas. 1.4min 8.6h 27.1d 91.7d 0 not stated book c 868,974 not meas. 1.2min 7.5h 27.1d 91.7d 0 not stated book e 157,347 not meas. 63ms 4.1s 10.5min 1.5d 0 not stated book h 152,984 not meas. 19ms 75ms 670ms 10.3s 0 not stated last_trade_price a 66,014 not meas. 47ms 888ms 7.9s 13.0s 0 not stated last_trade_price c 68,889 not meas. 9ms 39ms 213ms 4.8s 0 not stated last_trade_price e 72,072 not meas. 63ms 2.7s 11.9s 21.5s 0 not stated last_trade_price h 74,687 not meas. 19ms 81ms 568ms 10.2s 0 not stated market_resolved a 2,306 not meas. 38ms 7.9min 12.3min 12.4min 0 not stated market_resolved c 2,099 not meas. 4ms 10ms 3.2min 5.5min 0 not stated market_resolved e 2,155 not meas. 44ms 324ms 56.6s 1.0min 0 not stated market_resolved h 2,155 not meas. 13ms 54ms 184ms 5.0s 0 not stated new_market a 696 not meas. 241ms 28.1s 11.5min 12.3min 0 not stated new_market c 653 not meas. 79ms 20.3s 3.6min 2.2h 0 not stated new_market e 652 not meas. 204ms 17.5s 29.1s 7.7min 0 not stated new_market h 652 not meas. 123ms 18.0s 28.0s 1.7min 0 not stated price_change a 96,655,676 not meas. 37ms 63ms 682ms 13.0s 0 not stated price_change c 101,323,609 not meas. 4ms 9ms 92ms 13.5s 0 not stated price_change e 109,389,922 not meas. 44ms 211ms 6.4s 21.9s 0 not stated price_change h 110,583,772 not meas. 13ms 31ms 138ms 10.9s 0 not stated tick_size_change a 11,026 not meas. 36ms 40ms 111ms 643ms 0 not stated tick_size_change c 11,494 not meas. 4ms 7ms 18ms 80ms 0 not stated tick_size_change e 11,922 not meas. 44ms 117ms 476ms 9.6s 0 not stated tick_size_change h 11,930 not meas. 13ms 19ms 58ms 258ms 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/15/2026-08-29T15.parquet sha256sum 2026-08-29T15.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.