Hour audit: 2026-08-29T01
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-29T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T01:00:00.038778239+00:00 · last event 2026-08-29T01:59:59.999976053+00:00
VOLUME 119,206,922 rows · 1,317,268,926 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured h: 117,879,742 · e: 117,200,232 · c: 113,354,292 · a: 108,596,900 · b: 7,175,778 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · e: not measured · c: not measured · a: not measured · b: not measured (rows of the merged file that came from it; these partition it)
35 product-machine pairs publish no supplied count, and the figures above do not reconcile to the file's row count, so the split is incomplete by an unrecorded amount
INTEGRITY sha256 f4e7e9ef83de2513a7351f969e2d3967c5b1f21853e79f0f1014de1d265a0426
the corpus checksum ledger names this file with the same digest
joined 119,208,878 to merged 119,206,922, minus 1,956 (minus 0.0016%)
boundary drops 1,956 · 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 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 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
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 9,258,149 113,354,248 0-35 6feacfff5b82bc799de90da725ef2e47c4c9e7f7a82909be52d9a8030e7fc942 book 1,423,894 88,621,317 36-41 cfddaa5f96ec9c8562ffbb2cb9e7a937615596ba5c084f04d4ead2f7f64328fb last_trade_price 56,825 3,235,222 42-42 cabf12bead00eb650d88975c3fe93dab3da0bb31bfdb38e4fece1a651dc79ee9 market_resolved 1,375 198,258 43-43 9d2379e8651db74995969a67cced676ce4e49280c81f1df4aefa60b64eae13be new_market 9,535 399,482 44-44 1310d52d6addf86a3c1a22aa538ba00ffde8f7bf09acf5114f0927dff9c5c5ca price_change 108,452,188 1,109,920,059 45-458 787cac1ad28c9513932815c504f5c3d0f69f963469b126740b5c1b4f6abc6fa5 tick_size_change 4,956 181,404 459-459 ed492526420bc108df954a2ad2a5672360a870ac3bfcec1c83d00500b789c3b9 EVENT MIX count share price_change 108,452,188 90.98% best_bid_ask 9,258,149 7.77% book 1,423,894 1.19% last_trade_price 56,825 0.05% new_market 9,535 <0.01% tick_size_change 4,956 <0.01% market_resolved 1,375 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,258,235 9,258,149 86 68,853 FULL book 1,424,254 1,423,894 360 181,712 FULL last_trade_price 56,826 56,825 1 2,991 FULL market_resolved 1,375 1,375 0 1,184 FULL new_market 9,538 9,535 3 1,714 FULL price_change 108,453,694 108,452,188 1,506 54,146 FULL tick_size_change 4,956 4,956 0 1,160 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,444,267 not meas. 38ms 55ms 266ms 12.9s 0 not stated best_bid_ask b 580,876 not meas. 52ms 114ms 497ms 8.8s 0 not stated best_bid_ask c 8,904,890 not meas. 4ms 8ms 74ms 2.5s 0 not stated best_bid_ask e 9,229,226 not meas. 45ms 151ms 4.1s 21.0s 0 not stated best_bid_ask h 9,257,545 not meas. 12ms 21ms 103ms 8.4s 0 not stated book a 846,241 not meas. 1.3min 7.8h 26.6d 91.1d 0 not stated book b 875,436 not meas. 1.7min 13.6h 26.6d 91.1d 0 not stated book c 484,404 not meas. 51.0s 4.6h 25.3d 91.1d 0 not stated book e 118,569 not meas. 79ms 7.2s 37.0min 9.5d 0 not stated book h 124,050 not meas. 19ms 243ms 21.7min 72.6d 0 not stated last_trade_price a 51,979 not meas. 56ms 1.5s 8.8s 13.0s 0 not stated last_trade_price b 2,648 not meas. 86ms 1.8s 7.0s 8.7s 0 not stated last_trade_price c 54,491 not meas. 9ms 40ms 200ms 5.0s 0 not stated last_trade_price e 53,853 not meas. 75ms 4.1s 12.8s 20.9s 0 not stated last_trade_price h 56,772 not meas. 18ms 88ms 674ms 5.1s 0 not stated market_resolved a 1,291 not meas. 46ms 659ms 8.0min 8.4min 0 not stated market_resolved b 39 not meas. 55ms 430ms 749ms 762ms 0 not stated market_resolved c 1,221 not meas. 4ms 9ms 3.2min 6.3min 0 not stated market_resolved e 1,223 not meas. 48ms 293ms 3.0s 1.1min 0 not stated market_resolved h 1,223 not meas. 14ms 53ms 162ms 587ms 0 not stated new_market a 775 not meas. 158ms 15.4s 1.5h 3.3h 0 not stated new_market b 8,936 not meas. 1.3h 2.1h 2.3h 2.5h 0 not stated new_market c 767 not meas. 48ms 14.8s 2.8min 3.1h 0 not stated new_market e 764 not meas. 173ms 16.5s 22.9s 1.9h 0 not stated new_market h 764 not meas. 63ms 15.7s 22.1s 2.2h 0 not stated price_change a 99,247,951 not meas. 38ms 66ms 548ms 13.0s 0 not stated price_change b 5,707,527 not meas. 52ms 134ms 793ms 8.8s 0 not stated price_change c 103,903,891 not meas. 4ms 8ms 77ms 4.7s 0 not stated price_change e 107,791,653 not meas. 46ms 236ms 6.4s 21.1s 0 not stated price_change h 108,434,432 not meas. 12ms 21ms 121ms 8.4s 0 not stated tick_size_change a 4,396 not meas. 38ms 43ms 153ms 3.6s 0 not stated tick_size_change b 316 not meas. 52ms 224ms 583ms 588ms 0 not stated tick_size_change c 4,628 not meas. 4ms 6ms 20ms 77ms 0 not stated tick_size_change e 4,944 not meas. 46ms 121ms 2.0s 10.8s 0 not stated tick_size_change h 4,956 not meas. 12ms 18ms 54ms 791ms 0 not stated
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-29/01/2026-08-29T01.parquet sha256sum 2026-08-29T01.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.