Hour audit: 2026-08-28T21
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-28T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T21:00:00.035575941+00:00 · last event 2026-08-28T21:59:59.999994370+00:00
VOLUME 85,382,617 rows · 867,099,978 bytes (826.93 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 85,355,269 · h: 85,351,125 · a: 85,246,275 · b: 85,191,611 · e: 84,294,596 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: not measured · a: not measured · b: not measured · e: 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 8715d54036fd3e9c1d32255a0e4320c56e898bbb25bf690819860392f45e9b35
the corpus checksum ledger names this file with the same digest
joined 85,384,207 to merged 85,382,617, minus 1,590 (minus 0.0019%)
boundary drops 1,590 · 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,173,012 75,771,627 0-23 51cdde902a03a6d7c9ba7da1982475b1145539d1f0ce725e61709b2a9f69c06c book 146,690 14,017,905 24-24 22772978da547fdba4efcfe94d6eabb8d72d32ef9aedf90711ce49c80c56b6d3 last_trade_price 61,947 3,501,967 25-25 d872614643571e52dcd73ca1b21cda079098783759cd3a065b33c5d3db2f6362 market_resolved 1,863 283,193 26-26 ea5fd6dd0831b1f5a575b944bf613c427b4c34794bb19cdd2f68bcbe4b734af3 new_market 493 52,951 27-27 6816f616360efd57496e0adf375eb2660ea7025ef52cb311f945eca1643554c3 price_change 78,996,276 772,407,777 28-329 a3a2aa368d560005f9ef1d83ef24ca9c7bf91493341029e8dddb11ec97048e15 tick_size_change 2,336 86,459 330-330 9c648d81dcbb87b5c42a1206d7342b35bcae46c4568b1a294f466e72719db9d7 EVENT MIX count share price_change 78,996,276 92.52% best_bid_ask 6,173,012 7.23% book 146,690 0.17% last_trade_price 61,947 0.07% tick_size_change 2,336 <0.01% market_resolved 1,863 <0.01% new_market 493 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,173,121 6,173,012 109 63 FULL book 146,698 146,690 8 4,121 FULL last_trade_price 61,948 61,947 1 2 FULL market_resolved 1,863 1,863 0 4 FULL new_market 493 493 0 0 FULL price_change 78,997,748 78,996,276 1,472 136 FULL tick_size_change 2,336 2,336 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,169,121 not meas. 38ms 55ms 339ms 14.9s 0 not stated best_bid_ask b 6,167,585 not meas. 50ms 74ms 464ms 21.0s 0 not stated best_bid_ask c 6,172,754 not meas. 4ms 9ms 65ms 1.9s 0 not stated best_bid_ask e 6,144,540 not meas. 43ms 132ms 2.8s 39.4s 0 not stated best_bid_ask h 6,172,551 not meas. 12ms 21ms 108ms 6.6s 0 not stated book a 128,952 not meas. 66ms 3.0s 25.1min 72.5d 0 not stated book b 127,466 not meas. 88ms 4.5s 11.2min 72.5d 0 not stated book c 128,029 not meas. 6ms 21ms 258ms 72.3d 0 not stated book e 126,761 not meas. 120ms 11.1s 2.4h 1.0d 0 not stated book h 128,801 not meas. 20ms 182ms 10.8s 72.5d 0 not stated last_trade_price a 60,690 not meas. 62ms 2.1s 9.9s 14.9s 0 not stated last_trade_price b 60,132 not meas. 82ms 3.1s 14.3s 21.0s 0 not stated last_trade_price c 61,890 not meas. 9ms 38ms 173ms 5.0s 0 not stated last_trade_price e 56,447 not meas. 86ms 5.9s 15.1s 21.1s 0 not stated last_trade_price h 61,787 not meas. 18ms 149ms 927ms 6.5s 0 not stated market_resolved a 1,761 not meas. 38ms 223ms 580ms 2.1s 0 not stated market_resolved b 1,761 not meas. 50ms 259ms 703ms 7.8s 0 not stated market_resolved c 1,761 not meas. 4ms 13ms 54.8s 58.1s 0 not stated market_resolved e 1,757 not meas. 44ms 532ms 56.7s 59.9s 0 not stated market_resolved h 1,761 not meas. 12ms 53ms 178ms 762ms 0 not stated new_market a 321 not meas. 233ms 17.6s 50.1s 102.2d 0 not stated new_market b 321 not meas. 273ms 11.7s 19.0s 102.2d 0 not stated new_market c 321 not meas. 50ms 11.3s 17.8s 102.2d 0 not stated new_market e 321 not meas. 192ms 12.2s 20.7s 102.2d 0 not stated new_market h 321 not meas. 90ms 403ms 31.4min 102.2d 0 not stated price_change a 78,883,098 not meas. 38ms 69ms 2.0s 14.9s 0 not stated price_change b 78,832,014 not meas. 50ms 96ms 3.2s 21.1s 0 not stated price_change c 78,988,182 not meas. 4ms 7ms 82ms 2.0s 0 not stated price_change e 77,962,450 not meas. 43ms 173ms 8.1s 51.0s 0 not stated price_change h 78,983,568 not meas. 12ms 20ms 190ms 7.7s 0 not stated tick_size_change a 2,332 not meas. 37ms 44ms 224ms 782ms 0 not stated tick_size_change b 2,332 not meas. 49ms 62ms 194ms 644ms 0 not stated tick_size_change c 2,332 not meas. 4ms 6ms 125ms 365ms 0 not stated tick_size_change e 2,320 not meas. 43ms 117ms 10.1s 12.2s 0 not stated tick_size_change h 2,336 not meas. 12ms 17ms 56ms 343ms 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-28/21/2026-08-28T21.parquet sha256sum 2026-08-28T21.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.