Hour audit: 2026-10-07T10
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 and the manifest disagree on this file's digest. The checksum ledger and this hour's manifest publish DIFFERENT digests for the same file. One of the two is wrong and the file should not be trusted until that is resolved.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-07T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-07T10:00:00.000023878+00:00 · last event 2026-10-07T10:59:59.999948944+00:00
VOLUME 116,675,732 rows · 1,374,200,877 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 115,910,973 · m: 115,865,558 · h: 115,791,088 · i: 115,441,776 · n: 110,766,175 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 56,848,585 (48.72%) · m: 57,734,806 (49.48%) · h: 1,066,894 (0.91%) · i: 521,881 (0.45%) · n: 503,566 (0.43%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 d50370b4eb41db4dfc60d4ea49f21f6ab14934e4891f7fc6d9d21f89144bdeda
the corpus checksum ledger names this file with a DIFFERENT digest
joined 116,677,095 to merged 116,675,732, minus 1,363 (minus 0.0012%)
boundary drops 1,363 · 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-09T02:01:26Z 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 and the manifest disagree on this file's digest
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 10,491,742 134,690,414 0-40 a3f07da385e6e195623e60145fbaedd43c1fc11dbfb7d418de04f9f9fd75f9fe book 1,099,873 83,872,093 41-45 f241cabc7134a16cf68b38196b370195871d1894ace6b52b25db4412a0074830 last_trade_price 55,099 3,146,190 46-46 10a6ebe3c0ef44f177e34e9761ca379d7136c367122ebe31ffe43a5e600b7741 market_resolved 797 118,590 47-47 e46b8c119dd4ec3d463e4e907050e89cd54c710ab0beb9e187f0a55dbee4d950 new_market 757 75,240 48-48 620b117e538d1115dff6987c93770a7691a83f82d18a26b755b33cf03227be3f price_change 105,024,604 1,150,859,920 49-449 f8144dd35f26fc2b68e550704011faffc5aa753fe4371060b497a063ca7b2098 tick_size_change 2,860 105,937 450-450 1d420054a7a82e7e66d180a342692b4118897f63c10a6439c687611d30b52aad EVENT MIX count share price_change 105,024,604 90.01% best_bid_ask 10,491,742 8.99% book 1,099,873 0.94% last_trade_price 55,099 0.05% tick_size_change 2,860 <0.01% market_resolved 797 <0.01% new_market 757 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,491,838 10,491,742 96 579 FULL book 1,100,131 1,099,873 258 259,521 FULL last_trade_price 55,099 55,099 0 58 FULL market_resolved 798 797 1 1 FULL new_market 757 757 0 0 FULL price_change 105,025,612 105,024,604 1,008 390 FULL tick_size_change 2,860 2,860 0 10 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,488,802 77,632 18ms 30ms 245ms 51.6s 0 transport_latency_assumed best_bid_ask i 10,487,290 42,905 21ms 34ms 266ms 31.6s 0 transport_latency_assumed best_bid_ask m 10,490,498 5,253,890 5ms 15ms 118ms 5.0s 0 transport_latency_assumed best_bid_ask n 10,053,275 3,516 43ms 70ms 540ms 43.8s 0 transport_latency_assumed best_bid_ask o 10,490,185 5,113,799 5ms 15ms 125ms 6.0s 0 transport_latency_assumed book h 344,839 164,222 3.0min 1.4d 45.9d 130.5d 0 book_staleness book i 176,514 35,294 129ms 12.0h 31.9d 112.0d 0 book_staleness book m 359,510 224,253 3.5min 1.4d 45.9d 130.5d 0 book_staleness book n 789,895 452,522 21.1min 1.9d 45.9d 130.5d 0 book_staleness book o 361,141 223,582 3.6min 1.4d 45.9d 130.5d 0 book_staleness last_trade_price h 54,798 440 21ms 199ms 3.2s 23.0s 0 transport_latency_assumed last_trade_price i 53,833 167 28ms 661ms 11.3s 31.6s 0 transport_latency_assumed last_trade_price m 55,045 28,203 7ms 24ms 226ms 3.6s 0 transport_latency_assumed last_trade_price n 49,264 33 58ms 2.2s 15.4s 43.4s 0 transport_latency_assumed last_trade_price o 55,004 26,256 7ms 27ms 274ms 6.0s 0 transport_latency_assumed market_resolved h 728 1 21ms 22.1s 57.8s 57.8s 0 transport_latency_assumed market_resolved i 728 39 23ms 16.6s 52.6s 52.7s 0 transport_latency_assumed market_resolved m 728 397 6ms 16.8s 52.9s 52.9s 0 transport_latency_assumed market_resolved n 736 56 46ms 34.2s 5.4min 6.3min 0 transport_latency_assumed market_resolved o 728 304 6ms 24.4s 52.8s 52.8s 0 transport_latency_assumed new_market h 475 129 104ms 16.0s 41.8s 1.7min 0 transport_latency_assumed new_market i 475 158 98ms 10.3s 1.3min 1.6min 0 transport_latency_assumed new_market m 475 212 48ms 15.3s 1.1min 1.6min 0 transport_latency_assumed new_market n 475 37 230ms 18.8s 41.9s 1.5min 0 transport_latency_assumed new_market o 475 221 57ms 14.0s 20.2s 21.1s 0 transport_latency_assumed price_change h 104,898,586 824,462 19ms 40ms 628ms 54.5s 0 transport_latency_assumed price_change i 104,720,076 443,314 22ms 52ms 1.3s 31.7s 0 transport_latency_assumed price_change m 104,956,442 52,226,412 6ms 17ms 152ms 5.2s 0 transport_latency_assumed price_change n 99,869,710 47,398 44ms 116ms 4.7s 44.0s 0 transport_latency_assumed price_change o 105,000,580 51,483,018 6ms 17ms 169ms 7.9s 0 transport_latency_assumed tick_size_change h 2,860 8 18ms 27ms 69ms 10.8s 0 transport_latency_assumed tick_size_change i 2,860 4 22ms 36ms 83ms 977ms 0 transport_latency_assumed tick_size_change m 2,860 1,439 6ms 11ms 37ms 157ms 0 transport_latency_assumed tick_size_change n 2,820 4 43ms 57ms 129ms 460ms 0 transport_latency_assumed tick_size_change o 2,860 1,405 6ms 13ms 43ms 218ms 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-07/10/2026-10-07T10.parquet sha256sum 2026-10-07T10.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.