Hour audit: 2026-08-31T20
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 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-31T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T20:00:00.037655195+00:00 · last event 2026-08-31T20:59:59.999998345+00:00
VOLUME 78,445,653 rows · 827,676,423 bytes (789.33 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 78,418,145 · h: 78,302,398 · e: 77,680,577 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 75,862 (0.10%) · h: 690,150 (0.88%) · e: 77,679,641 (99.02%) (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 78,445,653 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 324f7589c807f3c117b2140ef1249590de3c7356c6762aa94803c89e29bb0f3f
the corpus checksum ledger names this file with the same digest
joined 78,446,597 to merged 78,445,653, minus 944 (minus 0.0012%)
boundary drops 944 · 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-09-02T03:58:03Z as ceh
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 6,788,176 86,218,593 0-25 766a9579463c885ed5705d89c7cbf0a6b2b497c4298e42096a3c9ae498e7ff48 book 220,101 22,338,794 26-26 d91c03f1c39510e7d33cb309aaee7eb25ad149a30081a9a4ee01a30beab08fb2 last_trade_price 73,196 4,122,190 27-27 4c813bdad20197b74ed3382799595b55447563c91f7124d7d1fcbf3968317103 market_resolved 2,031 319,509 28-28 79356a95088d7afba1401c939e00d7c5d2ae738fe9bd6c65d4b12ddc167adc05 new_market 1,985 222,994 29-29 45e2f8efd1555a93a12f305e0bb18fd603450170697e158fc5c943abfb177790 price_change 71,356,376 713,421,612 30-302 aa3bc865d21c8b9a662384469fcd98e31d3bd18b0b185fe49c78a69b08efdddb tick_size_change 3,788 137,192 303-303 3f5541a27bc38f9dfc5b7fe08191e5a5d81849b73bcf23340264cf5f1029976c EVENT MIX count share price_change 71,356,376 90.96% best_bid_ask 6,788,176 8.65% book 220,101 0.28% last_trade_price 73,196 0.09% tick_size_change 3,788 <0.01% market_resolved 2,031 <0.01% new_market 1,985 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,788,250 6,788,176 74 120,862 PARTIAL book 220,104 220,101 3 36,266 PARTIAL last_trade_price 73,197 73,196 1 4,470 PARTIAL market_resolved 2,031 2,031 0 1,994 PARTIAL new_market 1,985 1,985 0 1,449 PARTIAL price_change 71,357,242 71,356,376 866 152,839 PARTIAL tick_size_change 3,788 3,788 0 947 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,787,848 516 5ms 9ms 179ms 9.4s 0 transport_latency_assumed best_bid_ask e 6,781,291 6,781,219 44ms 100ms 1.1s 32.9s 0 transport_latency_assumed best_bid_ask h 6,787,628 6,441 13ms 23ms 328ms 40.7s 0 transport_latency_assumed book c 201,652 48,658 9ms 3.4min 19.2d 93.9d 0 book_staleness book e 164,195 164,192 67ms 8.6s 45.6min 92.3d 0 book_staleness book h 156,476 7,251 20ms 206ms 4.3min 93.9d 0 book_staleness last_trade_price c 73,150 9 10ms 42ms 258ms 5.0s 0 transport_latency_assumed last_trade_price e 71,909 71,908 64ms 2.1s 12.0s 33.0s 0 transport_latency_assumed last_trade_price h 73,173 1,279 19ms 116ms 905ms 13.5s 0 transport_latency_assumed market_resolved c 1,994 19 5ms 13ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 1,991 1,991 45ms 365ms 52.4s 1.0min 0 transport_latency_assumed market_resolved h 1,994 21 14ms 55ms 53.6s 57.0s 0 transport_latency_assumed new_market c 1,449 90 105ms 13.2s 30.5s 3.9min 0 transport_latency_assumed new_market e 1,449 1,449 289ms 12.5s 18.2s 3.0min 0 transport_latency_assumed new_market h 1,449 446 190ms 13.3s 26.6s 4.6min 0 transport_latency_assumed price_change c 71,348,264 26,570 5ms 11ms 221ms 13.0s 0 transport_latency_assumed price_change e 70,655,954 70,655,094 45ms 173ms 5.7s 33.0s 0 transport_latency_assumed price_change h 71,277,890 674,712 13ms 29ms 369ms 43.2s 0 transport_latency_assumed tick_size_change c 3,788 not meas. 5ms 8ms 219ms 565ms 0 transport_latency_assumed tick_size_change e 3,788 3,788 44ms 110ms 747ms 9.9s 0 transport_latency_assumed tick_size_change h 3,788 not meas. 13ms 18ms 127ms 647ms 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-31/20/2026-08-31T20.parquet sha256sum 2026-08-31T20.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.