Hour audit: 2026-08-29T00
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-29T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T00:00:00.035494422+00:00 · last event 2026-08-29T00:59:59.999978151+00:00
VOLUME 121,913,083 rows · 1,364,883,510 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured h: 120,203,156 · e: 119,307,917 · c: 110,590,120 · a: 105,497,388 · b: 3,115,318 (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 · b: not measured (rows of the merged file that came from it; these partition it)
35 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 4d60eb68d5f63becca4acc015a7d39dfaddc8c7d8dd7edca34a61cf27c9279f7
the corpus checksum ledger names this file with the same digest
joined 121,914,624 to merged 121,913,083, minus 1,541 (minus 0.0013%)
boundary drops 1,541 · 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 8,639,498 108,257,861 0-32 a39d7561cf084623f2769e9ee53b0e0074b91b55a36ffdac45d6be8602ee13b5 book 1,850,344 99,186,420 33-40 b3cc3a69361621e36901e542848a099227d2c82892c79209c6735f4dfd4d1b27 last_trade_price 70,901 3,969,762 41-41 7e3dba96994e66a8656f73a479b511a0cd3d44492aab18c221e24ff3df3cc7ca market_resolved 1,149 131,868 42-42 5512488224d2cf1e7afaac856eefee2161ea54de6488ffcfe27d4a757f1649fb new_market 3,919 271,693 43-43 37600464ebc8429867ce428dc6ff234b60c397bf157ec933257d88d444879578 price_change 111,343,912 1,151,558,287 44-468 72837995fd222961a8d95b4229a02278ef7b8926fd45d9d1e832d42c8afc8a0a tick_size_change 3,360 120,042 469-469 9cf4af647b820181baea195f1062623475d2178249562d0357d7234241009020 EVENT MIX count share price_change 111,343,912 91.33% best_bid_ask 8,639,498 7.09% book 1,850,344 1.52% last_trade_price 70,901 0.06% new_market 3,919 <0.01% tick_size_change 3,360 <0.01% market_resolved 1,149 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,639,590 8,639,498 92 82,850 FULL book 1,850,368 1,850,344 24 181,274 FULL last_trade_price 70,902 70,901 1 3,395 FULL market_resolved 1,149 1,149 0 779 FULL new_market 3,923 3,919 4 857 FULL price_change 111,345,332 111,343,912 1,420 75,329 FULL tick_size_change 3,360 3,360 0 824 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,580,952 not meas. 38ms 62ms 419ms 23.3s 0 not stated best_bid_ask b 202,348 not meas. 52ms 77ms 372ms 9.6s 0 not stated best_bid_ask c 7,912,455 not meas. 4ms 10ms 111ms 1.9s 0 not stated best_bid_ask e 8,597,355 not meas. 44ms 207ms 6.7s 24.6s 0 not stated best_bid_ask h 8,639,145 not meas. 12ms 25ms 176ms 41.2s 0 not stated book a 1,215,119 not meas. 1.9min 12.8h 26.5d 91.1d 0 not stated book b 385,186 not meas. 2.2min 16.5h 26.5d 91.1d 0 not stated book c 875,743 not meas. 1.5min 11.6h 26.5d 91.1d 0 not stated book e 151,021 not meas. 130ms 9.3s 3.7h 9.5d 0 not stated book h 154,838 not meas. 20ms 217ms 4.0h 72.6d 0 not stated last_trade_price a 61,294 not meas. 63ms 2.1s 8.3s 23.4s 0 not stated last_trade_price b 2,249 not meas. 78ms 2.8s 8.9s 9.7s 0 not stated last_trade_price c 65,087 not meas. 10ms 41ms 195ms 5.2s 0 not stated last_trade_price e 66,974 not meas. 98ms 5.6s 18.6s 22.9s 0 not stated last_trade_price h 70,854 not meas. 19ms 109ms 599ms 5.6s 0 not stated market_resolved a 863 not meas. 41ms 8.1min 11.3min 12.2min 0 not stated market_resolved b 8 not meas. 60ms 246ms 506ms 535ms 0 not stated market_resolved c 898 not meas. 5ms 5.9min 9.6min 9.6min 0 not stated market_resolved e 787 not meas. 44ms 537ms 1.0min 1.0min 0 not stated market_resolved h 787 not meas. 13ms 65ms 139ms 368ms 0 not stated new_market a 968 not meas. 209ms 5.1min 1.3h 3.5h 0 not stated new_market b 3,085 not meas. 1.1h 1.7h 2.1h 2.5h 0 not stated new_market c 872 not meas. 96ms 34.7s 48.1min 2.9h 0 not stated new_market e 852 not meas. 196ms 17.5s 41.9s 1.8h 0 not stated new_market h 852 not meas. 110ms 16.2s 36.2s 38.1min 0 not stated price_change a 96,635,276 not meas. 38ms 76ms 963ms 23.4s 0 not stated price_change b 2,522,378 not meas. 52ms 92ms 769ms 9.7s 0 not stated price_change c 101,731,917 not meas. 4ms 9ms 146ms 2.6s 0 not stated price_change e 110,487,576 not meas. 44ms 384ms 8.6s 24.6s 0 not stated price_change h 111,333,320 not meas. 13ms 25ms 238ms 41.2s 0 not stated tick_size_change a 2,916 not meas. 37ms 42ms 108ms 296ms 0 not stated tick_size_change b 64 not meas. 50ms 53ms 61ms 61ms 0 not stated tick_size_change c 3,148 not meas. 4ms 7ms 25ms 132ms 0 not stated tick_size_change e 3,352 not meas. 44ms 114ms 2.4s 19.7s 0 not stated tick_size_change h 3,360 not meas. 12ms 17ms 60ms 135ms 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/00/2026-08-29T00.parquet sha256sum 2026-08-29T00.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.