Hour audit: 2026-08-30T00
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-30T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T00:00:00.024233691+00:00 · last event 2026-08-30T00:59:59.999994878+00:00
VOLUME 119,893,558 rows · 1,249,601,186 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 119,539,838 · h: 119,467,544 · e: 119,413,069 · a: 114,967,542 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 60,369 (0.05%) · h: 72,989 (0.06%) · e: 119,412,120 (99.60%) · a: 348,080 (0.29%) (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,893,558 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 8dfa31780dde51eb3adcbc28d817e6b22bcea6d6a427509999f5bb88c2cd67a4
the corpus checksum ledger names this file with the same digest
joined 119,894,565 to merged 119,893,558, minus 1,007 (minus 0.0008%)
boundary drops 1,007 · 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-30T04:54:51Z 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,736,973 120,177,181 0-40 f92303526b7b7286907985167152bd84a5e824423abd55b1890a331b2c8ee5ab book 480,240 50,593,383 41-42 8db6a6b762549c6369ea1d222aab2f04576539fac9b53fe7e46f7c24be67eedd last_trade_price 62,152 3,478,900 43-43 fe79caecf7f8b4cfb2e871d7adaa8f4c01e03d2943e6f34fcea054f64ee89e04 market_resolved 1,610 256,671 44-44 12a6ab87696a872d40412acc581fc8b20d5e701abb92e90d0b03cd8d930895f3 new_market 815 87,773 45-45 a32d373a3b1a668d7b881bba6848075d9869684c5b326423be78949c9e8bebaa price_change 108,606,852 1,073,467,855 46-460 a142199e1c0f8dbf04f0665c9b5536e3f57bd9b8fcec072cfdc31fd10722e73c tick_size_change 4,916 177,098 461-461 133b9c3ee04e311727e263acb67e7c7a8864be688ac153b13a1e5d67e2dc9464 EVENT MIX count share price_change 108,606,852 90.59% best_bid_ask 10,736,973 8.96% book 480,240 0.40% last_trade_price 62,152 0.05% tick_size_change 4,916 <0.01% market_resolved 1,610 <0.01% new_market 815 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,737,073 10,736,973 100 68,818 PARTIAL book 480,286 480,240 46 174,040 PARTIAL last_trade_price 62,153 62,152 1 3,669 PARTIAL market_resolved 1,610 1,610 0 1,516 PARTIAL new_market 815 815 0 555 PARTIAL price_change 108,607,712 108,606,852 860 129,051 PARTIAL tick_size_change 4,916 4,916 0 1,223 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 10,303,740 34 36ms 46ms 214ms 17.1s 0 transport_latency_assumed best_bid_ask c 10,736,859 348 3ms 6ms 43ms 1.5s 0 transport_latency_assumed best_bid_ask e 10,733,316 10,733,216 44ms 106ms 1.2s 20.9s 0 transport_latency_assumed best_bid_ask h 10,736,377 3,375 12ms 21ms 80ms 6.8s 0 transport_latency_assumed book a 467,332 345,751 57.2s 4.4h 27.2d 92.1d 0 book_staleness book c 130,192 3,100 6ms 21ms 2.8min 73.5d 0 book_staleness book e 127,962 127,960 82ms 3.2s 15.4s 10.1h 0 book_staleness book h 129,645 3,429 18ms 85ms 2.2min 73.5d 0 book_staleness last_trade_price a 58,306 5 52ms 1.4s 8.7s 17.1s 0 transport_latency_assumed last_trade_price c 62,128 4 8ms 34ms 158ms 5.0s 0 transport_latency_assumed last_trade_price e 61,859 61,858 75ms 3.0s 13.4s 20.9s 0 transport_latency_assumed last_trade_price h 62,065 285 18ms 70ms 514ms 5.5s 0 transport_latency_assumed market_resolved a 1,496 50 36ms 183ms 4.8min 5.8min 0 transport_latency_assumed market_resolved c 1,516 29 3ms 9ms 55.8s 1.0min 0 transport_latency_assumed market_resolved e 1,515 1,515 44ms 370ms 50.2s 1.0min 0 transport_latency_assumed market_resolved h 1,516 16 12ms 78ms 51.5s 54.7s 0 transport_latency_assumed new_market a 557 52 169ms 19.9s 30.2min 1.5h 0 transport_latency_assumed new_market c 551 80 39ms 16.9s 26.4s 21.8min 0 transport_latency_assumed new_market e 551 551 220ms 19.4s 26.6s 21.1min 0 transport_latency_assumed new_market h 551 132 90ms 17.9s 28.4s 32.8min 0 transport_latency_assumed price_change a 104,131,299 2,188 36ms 58ms 502ms 17.1s 0 transport_latency_assumed price_change c 108,603,676 56,808 3ms 7ms 56ms 1.6s 0 transport_latency_assumed price_change e 108,482,950 108,482,104 44ms 154ms 2.9s 20.9s 0 transport_latency_assumed price_change h 108,532,474 65,752 12ms 23ms 101ms 8.4s 0 transport_latency_assumed tick_size_change a 4,812 not meas. 36ms 43ms 487ms 920ms 0 transport_latency_assumed tick_size_change c 4,916 not meas. 3ms 6ms 22ms 214ms 0 transport_latency_assumed tick_size_change e 4,916 4,916 44ms 120ms 956ms 5.3s 0 transport_latency_assumed tick_size_change h 4,916 not meas. 12ms 18ms 80ms 598ms 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/00/2026-08-30T00.parquet sha256sum 2026-08-30T00.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.