Hour audit: 2026-08-30T18
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-30T18 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T18:00:00.044546169+00:00 · last event 2026-08-30T18:59:59.999990987+00:00
VOLUME 46,850,021 rows · 537,129,681 bytes (512.25 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured a: 46,616,131 · c: 46,550,542 · h: 46,501,655 · e: 46,435,834 (each machine's own feed; these overlap and do not sum to the file)
supplied a: 133,362 (0.28%) · c: 107,634 (0.23%) · h: 173,193 (0.37%) · e: 46,435,832 (99.12%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 46,850,021 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 c281514f569e61b003773ade47eed736a4cdad3ffcf10ed4db0e72b1c5e21c25
the corpus checksum ledger names this file with the same digest
joined 46,850,061 to merged 46,850,021, minus 40 (minus 0.0001%)
boundary drops 40 · 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-30T19:44:06Z 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 an incident recorded by the venue intersects this hour: Venue paused trading for about half an hour, 2026-08-30T17:55Z to 2026-08-30T18:29ZThe 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 4,390,636 61,722,340 0-16 cdd8b895cb521fbf0180b14b26b3d7dd85c9355d8553cbd2efc95e6bc0f7ba34 book 483,132 41,073,092 17-18 ff142600a1dd3b1d4dc3da0cc0bbb6959b6786aa0a0057cbdd8f9d72a08a3667 last_trade_price 40,905 2,536,770 19-19 51827c3665c7d0fac32551116c16f49a2c1a6188da78e59f9920c48710e623cc market_resolved 2,368 383,064 20-20 e58cbaf6642c74d7602e5bdef1d3aea920554bfb3f39d38fc5c6172518f02852 new_market 955 106,888 21-21 55ad7c755789e23be88eb767681214ad936eef2c75184dbfc5b40cf65aa0d7bb price_change 41,924,501 430,492,415 22-181 9617366172ff070fdc0911a67d60b206c6e5c855ced276327531acbce04be372 tick_size_change 7,524 274,513 182-182 e33114234f10d6a6471e412433ad25b86de5f48eb9778c2d4547c8d477a47f47 EVENT MIX count share price_change 41,924,501 89.49% best_bid_ask 4,390,636 9.37% book 483,132 1.03% last_trade_price 40,905 0.09% tick_size_change 7,524 0.02% market_resolved 2,368 <0.01% new_market 955 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 4,390,636 4,390,636 0 112,912 PARTIAL book 483,172 483,132 40 139,600 PARTIAL last_trade_price 40,905 40,905 0 4,499 PARTIAL market_resolved 2,368 2,368 0 2,326 PARTIAL new_market 955 955 0 680 PARTIAL price_change 41,924,501 41,924,501 0 148,358 PARTIAL tick_size_change 7,524 7,524 0 1,881 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 4,388,857 2 39ms 52ms 322ms 11.5s 0 transport_latency_assumed best_bid_ask c 4,390,237 291 5ms 8ms 127ms 2.9s 0 transport_latency_assumed best_bid_ask e 4,386,684 4,386,684 42ms 115ms 1.1s 20.3s 0 transport_latency_assumed best_bid_ask h 4,389,856 3,659 13ms 20ms 169ms 17.4s 0 transport_latency_assumed book a 273,583 130,160 1.7min 1.3h 27.1d 92.8d 0 book_staleness book c 206,861 96,517 42.5s 37.1min 22.3d 92.8d 0 book_staleness book e 177,413 177,411 7.7s 30.0min 22.2d 92.8d 0 book_staleness book h 172,788 79,044 1.4s 13.7min 22.2d 92.8d 0 book_staleness last_trade_price a 40,839 not meas. 48ms 567ms 4.6s 11.5s 0 transport_latency_assumed last_trade_price c 40,895 3 9ms 36ms 190ms 5.0s 0 transport_latency_assumed last_trade_price e 40,895 40,895 55ms 1.2s 7.5s 16.9s 0 transport_latency_assumed last_trade_price h 40,895 7 18ms 65ms 423ms 5.8s 0 transport_latency_assumed market_resolved a 2,326 41 41ms 166ms 515ms 59.5s 0 transport_latency_assumed market_resolved c 2,326 not meas. 5ms 7ms 155ms 59.6s 0 transport_latency_assumed market_resolved e 2,326 2,326 43ms 188ms 689ms 59.5s 0 transport_latency_assumed market_resolved h 2,326 1 14ms 27ms 113ms 42.1s 0 transport_latency_assumed new_market a 680 15 192ms 11.2s 16.9s 2.1min 0 transport_latency_assumed new_market c 680 132 48ms 13.0s 23.0s 5.6min 0 transport_latency_assumed new_market e 680 680 192ms 11.8s 18.0s 2.9min 0 transport_latency_assumed new_market h 680 128 81ms 12.7s 23.3s 5.0min 0 transport_latency_assumed price_change a 41,902,322 3,144 40ms 85ms 1.3s 11.5s 0 transport_latency_assumed price_change c 41,902,019 10,691 5ms 10ms 300ms 6.3s 0 transport_latency_assumed price_change e 41,820,312 41,820,312 42ms 165ms 3.4s 20.3s 0 transport_latency_assumed price_change h 41,887,586 90,354 13ms 24ms 425ms 17.4s 0 transport_latency_assumed tick_size_change a 7,524 not meas. 39ms 46ms 794ms 1.7s 0 transport_latency_assumed tick_size_change c 7,524 not meas. 5ms 8ms 308ms 788ms 0 transport_latency_assumed tick_size_change e 7,524 7,524 43ms 153ms 815ms 1.4s 0 transport_latency_assumed tick_size_change h 7,524 not meas. 13ms 19ms 426ms 2.1s 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/18/2026-08-30T18.parquet sha256sum 2026-08-30T18.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.