Hour audit: 2026-10-09T00
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
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T00:00:00.000012942+00:00 · last event 2026-10-09T00:59:59.999959219+00:00
VOLUME 144,584,764 rows · 1,707,281,660 bytes (1.59 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 144,458,130 · m: 144,400,471 · i: 144,396,048 · n: 144,382,793 · h: 144,380,408 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 71,809,714 (49.67%) · m: 69,537,730 (48.09%) · i: 1,191,411 (0.82%) · n: 99,972 (0.07%) · h: 1,945,937 (1.35%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 144,584,764 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0997e34bbee1472090058340307a7e010295ca3423100e4ea41b4acb3987ce64
no line in the corpus checksum ledger names this file
joined 144,585,945 to merged 144,584,764, minus 1,181 (minus 0.0008%)
boundary drops 1,181 · 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-10-09T20:38:59Z as himno
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
PASS every expected machine contributed
FINDING the checksum ledger does not name this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 14,162,581 180,006,021 0-54 baac608fd7cf667b34e0b7f04b1cebf185e3c39f62748bb375a4f2b4b89f5247 book 227,052 24,257,263 55-55 b6d417e4cab167e943a1080f2bc856349be7cd5cd435fc7c34e9d5a1f2ff551e last_trade_price 64,105 3,601,281 56-56 96e88ceb6e6dd8171728a95eda2bb5470ae1fb3971d9afb75146aadee1ab3fdc market_resolved 839 129,414 57-57 03aeef2daf46aad4d4fc2f5123277d2523252f6ea060a8d9e6ca0985ec8bb50c new_market 635 64,482 58-58 1fb790c1bf8ae020267f0d0d4cbfce0b9990c05d1002e5e3755e9442288ad9b1 price_change 130,126,736 1,497,476,990 59-555 78d756a6b9a85b60bc9d6dec10971ae1a301ee87c12ceb8427a70c209b15417d tick_size_change 2,816 101,185 556-556 e9059d289bdaf8847c03b8f6d59832c5919d7de3df1388d852d5a08fc6946eb7 EVENT MIX count share price_change 130,126,736 90.00% best_bid_ask 14,162,581 9.80% book 227,052 0.16% last_trade_price 64,105 0.04% tick_size_change 2,816 <0.01% market_resolved 839 <0.01% new_market 635 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,162,691 14,162,581 110 76 FULL book 227,056 227,052 4 43,945 FULL last_trade_price 64,105 64,105 0 0 FULL market_resolved 840 839 1 1 FULL new_market 635 635 0 0 FULL price_change 130,127,802 130,126,736 1,066 187 FULL tick_size_change 2,816 2,816 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 14,159,257 183,204 19ms 38ms 189ms 25.0s 0 transport_latency_assumed best_bid_ask i 14,161,230 104,722 22ms 39ms 151ms 3.0s 0 transport_latency_assumed best_bid_ask m 14,161,102 6,897,458 5ms 21ms 122ms 3.8s 0 transport_latency_assumed best_bid_ask n 14,160,234 5,814 45ms 68ms 232ms 11.4s 0 transport_latency_assumed best_bid_ask o 14,161,598 6,971,383 5ms 21ms 122ms 9.0s 0 transport_latency_assumed book h 141,184 13,534 24ms 731ms 20.4h 113.6d 0 book_staleness book i 146,528 17,987 26ms 1.1min 20.9h 132.1d 0 book_staleness book m 154,164 83,583 9ms 7.0min 13.0d 113.6d 0 book_staleness book n 149,647 20,773 55ms 3.5min 10.1d 132.1d 0 book_staleness book o 153,756 91,175 8ms 6.2min 13.1d 132.1d 0 book_staleness last_trade_price h 63,822 732 21ms 123ms 770ms 8.7s 0 transport_latency_assumed last_trade_price i 63,968 482 25ms 135ms 963ms 3.0s 0 transport_latency_assumed last_trade_price m 63,826 29,174 7ms 31ms 197ms 1.8s 0 transport_latency_assumed last_trade_price n 63,744 61 50ms 842ms 4.5s 10.6s 0 transport_latency_assumed last_trade_price o 63,979 33,656 6ms 30ms 183ms 2.1s 0 transport_latency_assumed market_resolved h 804 37 28ms 34.5s 56.1s 56.1s 0 transport_latency_assumed market_resolved i 805 143 32ms 28.3s 45.6s 45.7s 0 transport_latency_assumed market_resolved m 804 325 6ms 29.2s 46.6s 46.6s 0 transport_latency_assumed market_resolved n 805 1 59ms 34.7s 52.9s 57.7s 0 transport_latency_assumed market_resolved o 804 333 6ms 30.5s 48.3s 48.4s 0 transport_latency_assumed new_market h 401 96 60ms 13.4s 24.7s 1.9min 0 transport_latency_assumed new_market i 401 98 64ms 16.6s 1.5min 1.7min 0 transport_latency_assumed new_market m 401 214 39ms 14.8s 1.5min 1.6min 0 transport_latency_assumed new_market n 401 61 105ms 14.3s 48.1s 1.7min 0 transport_latency_assumed new_market o 401 166 49ms 15.4s 30.0s 1.9min 0 transport_latency_assumed price_change h 130,012,124 1,748,282 19ms 45ms 342ms 25.1s 0 transport_latency_assumed price_change i 130,020,300 1,067,962 22ms 47ms 313ms 3.0s 0 transport_latency_assumed price_change m 130,017,358 62,525,626 5ms 24ms 142ms 4.5s 0 transport_latency_assumed price_change n 130,005,146 73,262 45ms 84ms 935ms 11.6s 0 transport_latency_assumed price_change o 130,074,776 64,711,604 5ms 24ms 139ms 9.5s 0 transport_latency_assumed tick_size_change h 2,816 52 18ms 34ms 115ms 278ms 0 transport_latency_assumed tick_size_change i 2,816 17 22ms 38ms 138ms 1.1s 0 transport_latency_assumed tick_size_change m 2,816 1,350 5ms 22ms 138ms 263ms 0 transport_latency_assumed tick_size_change n 2,816 not meas. 44ms 68ms 222ms 594ms 0 transport_latency_assumed tick_size_change o 2,816 1,397 5ms 23ms 154ms 265ms 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-10-09/00/2026-10-09T00.parquet sha256sum 2026-10-09T00.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.