Hour audit: 2026-08-30T22
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-30T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T22:00:00.042897328+00:00 · last event 2026-08-30T22:59:59.999972372+00:00
VOLUME 103,494,662 rows · 1,066,473,374 bytes (1017.07 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 103,139,901 · h: 103,102,533 · e: 102,242,159 · a: 98,938,549 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 27,949 (0.03%) · h: 883,996 (0.85%) · e: 102,240,915 (98.79%) · a: 341,802 (0.33%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 103,494,662 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 ba97e69dd0cce6e2fe21d0a3a4d5b7570e64c258ab1291652d5a0ecf0b7e4490
the corpus checksum ledger names this file with the same digest
joined 103,495,978 to merged 103,494,662, minus 1,316 (minus 0.0013%)
boundary drops 1,316 · 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 merged 2026-08-30T23:54:50Z as aceh
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 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,135,354 103,086,343 0-34 ca28e96ba7bd2284f3e296c3eb7934f5e65efb46d8a72ba41e8900bb56f91386 book 504,710 51,764,604 35-36 e27cb2009eb4718ea881c7151fde32210b7f3ccc551981c700391b35883a81e3 last_trade_price 74,562 4,114,746 37-37 6e8cd4d5976e69e839f5b9b388d4846779c5f1e70fc9f20b87249c9694b047d4 market_resolved 2,269 343,578 38-38 e22d62539fc1246351377c715ca7c8a8037d9dfaf3efefdc3351d96e468fa8d1 new_market 807 88,915 39-39 a5cc09116df473dadb757dd35671f5ef9c221b0873a5ea8da1ee74680fcacb69 price_change 93,773,156 905,762,148 40-397 3bb8e33f1c4080c342b6510522101e09cca09bf2c850f28410c2e08e15abae43 tick_size_change 3,804 135,916 398-398 357d5afb5e3a550c87dbafbf68eb1f7d8a251c0906881235462ef63b792f964e EVENT MIX count share price_change 93,773,156 90.61% best_bid_ask 9,135,354 8.83% book 504,710 0.49% last_trade_price 74,562 0.07% tick_size_change 3,804 <0.01% market_resolved 2,269 <0.01% new_market 807 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,135,454 9,135,354 100 82,825 PARTIAL book 504,716 504,710 6 168,761 PARTIAL last_trade_price 74,562 74,562 0 3,627 PARTIAL market_resolved 2,269 2,269 0 2,153 PARTIAL new_market 807 807 0 578 PARTIAL price_change 93,774,366 93,773,156 1,210 132,732 PARTIAL tick_size_change 3,804 3,804 0 951 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,741,825 40 38ms 53ms 389ms 21.7s 0 transport_latency_assumed best_bid_ask c 9,135,064 564 0ms 3ms 59ms 5.1s 0 transport_latency_assumed best_bid_ask e 9,110,853 9,110,761 44ms 113ms 1.7s 25.5s 0 transport_latency_assumed best_bid_ask h 9,134,514 23,989 12ms 19ms 108ms 8.3s 0 transport_latency_assumed book a 482,972 339,079 43.0s 3.4h 27.2d 93.0d 0 book_staleness book c 154,646 637 2ms 17ms 256ms 74.4d 0 book_staleness book e 153,527 153,527 127ms 7.8s 2.1h 14.3d 0 book_staleness book h 156,224 11,467 19ms 121ms 13.9s 93.0d 0 book_staleness last_trade_price a 68,702 9 61ms 2.5s 11.6s 21.7s 0 transport_latency_assumed last_trade_price c 74,505 15 5ms 33ms 172ms 5.0s 0 transport_latency_assumed last_trade_price e 70,158 70,158 89ms 4.9s 14.8s 25.2s 0 transport_latency_assumed last_trade_price h 74,509 4,380 19ms 110ms 484ms 5.3s 0 transport_latency_assumed market_resolved a 2,153 49 39ms 168ms 4.3min 4.4min 0 transport_latency_assumed market_resolved c 2,153 65 0ms 2ms 48ms 614ms 0 transport_latency_assumed market_resolved e 2,153 2,153 45ms 284ms 54.6s 59.5s 0 transport_latency_assumed market_resolved h 2,153 2 12ms 41ms 56.6s 1.0min 0 transport_latency_assumed new_market a 580 38 184ms 18.5s 29.1s 43.6min 0 transport_latency_assumed new_market c 578 66 52ms 20.1s 25.1s 22.1min 0 transport_latency_assumed new_market e 578 578 168ms 20.0s 27.7s 33.9min 0 transport_latency_assumed new_market h 578 125 100ms 18.2s 25.0s 1.1h 0 transport_latency_assumed price_change a 89,638,641 2,587 38ms 81ms 2.3s 21.8s 0 transport_latency_assumed price_change c 93,769,151 26,602 0ms 4ms 104ms 5.8s 0 transport_latency_assumed price_change e 92,901,098 92,899,946 45ms 167ms 6.2s 25.6s 0 transport_latency_assumed price_change h 93,730,751 844,021 12ms 22ms 188ms 8.3s 0 transport_latency_assumed tick_size_change a 3,676 not meas. 38ms 44ms 144ms 409ms 0 transport_latency_assumed tick_size_change c 3,804 not meas. 0ms 3ms 32ms 498ms 0 transport_latency_assumed tick_size_change e 3,792 3,792 45ms 110ms 832ms 10.5s 0 transport_latency_assumed tick_size_change h 3,804 12 12ms 17ms 66ms 828ms 0 transport_latency_assumed
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-30/22/2026-08-30T22.parquet sha256sum 2026-08-30T22.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.