Hour audit: 2026-08-31T23
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-31T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T23:00:00.030847241+00:00 · last event 2026-08-31T23:59:59.130204102+00:00
VOLUME 18,807,687 rows · 223,696,096 bytes (213.33 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 18,781,893 · h: 18,683,394 · e: 18,653,054 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 95,274 (0.51%) · h: 61,820 (0.33%) · e: 18,650,593 (99.16%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 18,807,687 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 75799a47b669100526ed1e8632f25ad0fc57f4e2ff6198afe6e62aaaa13199df
the corpus checksum ledger names this file with the same digest
joined 18,811,194 to merged 18,807,687, minus 3,507 (minus 0.0186%)
boundary drops 3,507 · 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-02T04:26:28Z 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 an incident recorded by the venue intersects this hour: Venue paused trading, cancel-only mode, 2026-08-31T23:09Z to 2026-09-01T01:07ZThe 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 1,605,191 28,296,392 0-6 a65a58e489b9fef1d18327d2dcf9504efb15b51529d0f0456e9580973a1f72b5 book 142,949 16,090,877 7-7 4f5c88da63d342f8d406641ff614bc47a999869168313b0c01bdcdd21881d4bb last_trade_price 11,024 678,284 8-8 8bf4bcdb1ad4102a551e83f16aee977db00b0d67f93d058ccffc05dc955f91f7 market_resolved 1,200 191,254 9-9 4bf70aece924e14f18f6b201ff705fd3aca764c20e3ba180418ca5d77db01e09 new_market 1,715 174,082 10-10 417af17f977bfa7986d50be8ae461e6469ab3f96f9e2314c5176d651727d199c price_change 17,045,028 178,013,021 11-76 3c9d155653a53fe24dd65dc2a04fa6b50a55a57557c8ab1e9f81c37f604a4401 tick_size_change 580 21,721 77-77 c8624196c55b4deff59de59e207610c9d263b80294a10782bdb6089506b4c912 EVENT MIX count share price_change 17,045,028 90.63% best_bid_ask 1,605,191 8.53% book 142,949 0.76% last_trade_price 11,024 0.06% new_market 1,715 <0.01% market_resolved 1,200 <0.01% tick_size_change 580 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 1,605,462 1,605,191 271 95,024 PARTIAL book 143,053 142,949 104 58,321 PARTIAL last_trade_price 11,024 11,024 0 1,173 PARTIAL market_resolved 1,200 1,200 0 1,179 PARTIAL new_market 1,715 1,715 0 1,156 PARTIAL price_change 17,048,160 17,045,028 3,132 144,179 PARTIAL tick_size_change 580 580 0 145 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 1,605,125 126 4ms 8ms 246ms 3.4s 0 transport_latency_assumed best_bid_ask e 1,603,186 1,603,053 43ms 125ms 1.2s 23.5s 0 transport_latency_assumed best_bid_ask h 1,605,144 2,012 11ms 20ms 398ms 29.4s 0 transport_latency_assumed book c 119,208 87,412 21.4min 3.2h 29.4d 94.1d 0 book_staleness book e 43,454 43,362 3.6s 27.5min 2.3d 56.8d 0 book_staleness book h 36,916 12,175 57ms 26.8min 23.3d 94.1d 0 book_staleness last_trade_price c 11,021 not meas. 10ms 44ms 324ms 4.0s 0 transport_latency_assumed last_trade_price e 10,819 10,819 80ms 4.1s 17.4s 23.6s 0 transport_latency_assumed last_trade_price h 11,021 205 18ms 201ms 1.3s 5.3s 0 transport_latency_assumed market_resolved c 1,179 not meas. 5ms 9ms 59.4s 1.0min 0 transport_latency_assumed market_resolved e 1,179 1,179 43ms 314ms 59.5s 1.0min 0 transport_latency_assumed market_resolved h 1,179 21 13ms 34ms 51.2s 1.0min 0 transport_latency_assumed new_market c 1,156 163 84ms 26.7s 50.7s 1.4min 0 transport_latency_assumed new_market e 1,156 1,156 264ms 33.5s 52.9s 57.3s 0 transport_latency_assumed new_market h 1,156 396 169ms 30.4s 51.4s 1.3min 0 transport_latency_assumed price_change c 17,043,624 7,573 4ms 9ms 252ms 3.6s 0 transport_latency_assumed price_change e 16,992,680 16,990,444 43ms 175ms 2.7s 23.8s 0 transport_latency_assumed price_change h 17,027,398 47,011 12ms 25ms 410ms 29.4s 0 transport_latency_assumed tick_size_change c 580 not meas. 4ms 25ms 803ms 805ms 0 transport_latency_assumed tick_size_change e 580 580 43ms 594ms 2.8s 4.0s 0 transport_latency_assumed tick_size_change h 580 not meas. 12ms 284ms 867ms 902ms 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/23/2026-08-31T23.parquet sha256sum 2026-08-31T23.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.