Hour audit: 2026-08-30T01
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-30T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T01:00:00.032934656+00:00 · last event 2026-08-30T01:59:59.999991432+00:00
VOLUME 119,506,790 rows · 1,247,358,618 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 118,804,325 · h: 118,731,757 · e: 118,629,301 · a: 109,684,576 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 65,296 (0.05%) · h: 122,696 (0.10%) · e: 118,626,590 (99.26%) · a: 692,208 (0.58%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 119,506,790 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 0a9c36045e4b9e188302584ed135236c0a31eb3b943e14e81b5203135f05df9b
the corpus checksum ledger names this file with the same digest
joined 119,510,131 to merged 119,506,790, minus 3,341 (minus 0.0028%)
boundary drops 3,341 · 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-30T05:19:18Z 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 10,968,956 120,767,749 0-41 5f7add5520f85e41582546f6c613d71c281af8f2f0c313748810366cdd6aa0e0 book 818,916 58,815,074 42-45 7a0ff7331f9fe6d11ee2d8de9de9793cda3a4a43811c34ad14fde8d3c1a47a26 last_trade_price 58,766 3,324,223 46-46 3fd7ac38fa4d2b2a64a157f6c9697b03eb6902b3801d81c0a8e83737bab04556 market_resolved 1,782 262,727 47-47 c035ca8b95cc058322a9def2185d3e3ddd9e71653fb142d9fb5fd6f0d7929f6a new_market 666 72,728 48-48 dd845d674e96e3ae96121b353a25804ca46584067d91245cfe05c8c5f1e88917 price_change 107,651,752 1,062,540,133 49-459 6392fb5ac7109b772ad35511b1cb57e4507e0b8a912f7bc7c5cd04e24a291965 tick_size_change 5,952 216,729 460-460 f7cd35a0bcab22b8a3a0ebb7708be47c51294237cdbf08615f452fbe3e0fc27c EVENT MIX count share price_change 107,651,752 90.08% best_bid_ask 10,968,956 9.18% book 818,916 0.69% last_trade_price 58,766 0.05% tick_size_change 5,952 <0.01% market_resolved 1,782 <0.01% new_market 666 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,969,290 10,968,956 334 66,668 PARTIAL book 818,928 818,916 12 173,045 PARTIAL last_trade_price 58,767 58,766 1 3,638 PARTIAL market_resolved 1,782 1,782 0 1,658 PARTIAL new_market 666 666 0 463 PARTIAL price_change 107,654,746 107,651,752 2,994 128,668 PARTIAL tick_size_change 5,952 5,952 0 1,488 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 10,087,214 12 38ms 47ms 193ms 11.7s 0 transport_latency_assumed best_bid_ask c 10,968,794 289 4ms 7ms 42ms 1.9s 0 transport_latency_assumed best_bid_ask e 10,958,253 10,957,931 44ms 104ms 1.9s 18.4s 0 transport_latency_assumed best_bid_ask h 10,968,550 10,724 12ms 24ms 80ms 5.6s 0 transport_latency_assumed book a 804,504 688,214 1.6min 7.0h 27.6d 92.1d 0 book_staleness book c 124,220 3,787 6ms 24ms 8.9min 73.6d 0 book_staleness book e 121,023 121,017 73ms 3.2s 1.8min 21.6d 0 book_staleness book h 124,591 5,898 19ms 129ms 23.4min 73.6d 0 book_staleness last_trade_price a 54,685 3 55ms 1.7s 8.7s 11.7s 0 transport_latency_assumed last_trade_price c 58,754 6 9ms 36ms 181ms 5.0s 0 transport_latency_assumed last_trade_price e 57,992 57,991 70ms 2.8s 9.6s 18.3s 0 transport_latency_assumed last_trade_price h 58,717 766 19ms 82ms 679ms 5.0s 0 transport_latency_assumed market_resolved a 1,578 78 40ms 186ms 8.9min 9.1min 0 transport_latency_assumed market_resolved c 1,658 24 4ms 7ms 39ms 261ms 0 transport_latency_assumed market_resolved e 1,658 1,658 44ms 206ms 59.4s 1.2min 0 transport_latency_assumed market_resolved h 1,658 22 13ms 50ms 1.0min 1.0min 0 transport_latency_assumed new_market a 467 63 175ms 15.6s 6.0min 8.1min 0 transport_latency_assumed new_market c 463 40 45ms 15.5s 53.9s 1.1min 0 transport_latency_assumed new_market e 463 463 183ms 13.7s 21.4s 1.1min 0 transport_latency_assumed new_market h 463 100 85ms 12.4s 35.7s 1.2min 0 transport_latency_assumed price_change a 98,730,792 3,838 39ms 56ms 390ms 11.7s 0 transport_latency_assumed price_change c 107,644,484 61,150 4ms 7ms 50ms 2.0s 0 transport_latency_assumed price_change e 107,483,960 107,481,578 44ms 161ms 3.5s 18.4s 0 transport_latency_assumed price_change h 107,571,826 105,186 13ms 25ms 95ms 6.0s 0 transport_latency_assumed tick_size_change a 5,336 not meas. 38ms 44ms 113ms 394ms 0 transport_latency_assumed tick_size_change c 5,952 not meas. 4ms 6ms 17ms 221ms 0 transport_latency_assumed tick_size_change e 5,952 5,952 44ms 106ms 2.0s 9.1s 0 transport_latency_assumed tick_size_change h 5,952 not meas. 13ms 25ms 70ms 247ms 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/01/2026-08-30T01.parquet sha256sum 2026-08-30T01.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.