Hour audit: 2026-10-08T21
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-08T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T21:00:00.000030949+00:00 · last event 2026-10-08T21:59:59.999952564+00:00
VOLUME 116,026,948 rows · 1,312,060,751 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 115,713,827 · o: 115,660,310 · n: 115,604,879 · i: 115,536,383 · h: 115,495,771 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 57,426,042 (49.49%) · o: 57,093,063 (49.21%) · n: 142,824 (0.12%) · i: 618,467 (0.53%) · h: 746,552 (0.64%) (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 116,026,948 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 34cfe7480c868301079a0da0d49917002ce07f02b8e38ccdf047175b544d2852
the corpus checksum ledger names this file with the same digest
joined 116,028,571 to merged 116,026,948, minus 1,623 (minus 0.0014%)
boundary drops 1,623 · 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-08T23:02:30Z 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 8/8 pass
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
PASS the checksum ledger names 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 12,233,974 152,387,675 0-46 6af72a50b7bbc585b1939812b1ea0d937601e28d5b86eb86d43a98b4e72c8e12 book 349,149 36,166,581 47-48 6f54733b707bb8f4f144c6f92d1ae0ce5947ff3ced8c5d8192e980462db5ee99 last_trade_price 47,496 2,789,842 49-49 9361ca31d6083968e2599880a2511d93e15d79914bca9c25c8bff39d16de8bb4 market_resolved 931 149,344 50-50 f837661c2ba32d23f01bf099bbc06c82ffc4f47dae925a5dc31c44a138ecf9b8 new_market 1,336 129,120 51-51 a49c9a3f5f5ffcc57d6307c13b88e4090ce8ae57c78e35bfc17c2ac74912af11 price_change 103,391,726 1,119,028,567 52-446 e035aa4cf990f6b9218b9be5cb9ad8fb50ae285e046875b208d37c7bf83a2065 tick_size_change 2,336 86,174 447-447 19b3a30f71643c73861685e3a7c842ce22265d8edc7c734002258bab25bc022d EVENT MIX count share price_change 103,391,726 89.11% best_bid_ask 12,233,974 10.54% book 349,149 0.30% last_trade_price 47,496 0.04% tick_size_change 2,336 <0.01% new_market 1,336 <0.01% market_resolved 931 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,234,140 12,233,974 166 75 FULL book 349,187 349,149 38 105,907 FULL last_trade_price 47,497 47,496 1 2 FULL market_resolved 931 931 0 0 FULL new_market 1,336 1,336 0 0 FULL price_change 103,393,144 103,391,726 1,418 164 FULL tick_size_change 2,336 2,336 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,225,736 72,731 18ms 30ms 257ms 45.8s 0 transport_latency_assumed best_bid_ask i 12,225,109 57,601 21ms 30ms 139ms 3.9s 0 transport_latency_assumed best_bid_ask m 12,229,790 6,131,737 5ms 13ms 95ms 6.9s 0 transport_latency_assumed best_bid_ask n 12,230,527 5,844 44ms 62ms 265ms 29.4s 0 transport_latency_assumed best_bid_ask o 12,229,348 5,966,061 5ms 13ms 97ms 8.0s 0 transport_latency_assumed book h 139,829 41,269 44ms 5.5h 31.5d 132.0d 0 book_staleness book i 140,779 41,149 57ms 5.1h 31.5d 132.0d 0 book_staleness book m 172,017 114,018 35ms 11.2h 33.3d 132.0d 0 book_staleness book n 145,318 46,750 165ms 6.2h 31.5d 132.0d 0 book_staleness book o 161,254 105,963 17ms 8.8h 31.5d 132.0d 0 book_staleness last_trade_price h 46,467 319 21ms 235ms 1.5s 7.9s 0 transport_latency_assumed last_trade_price i 46,560 202 25ms 430ms 2.2s 3.4s 0 transport_latency_assumed last_trade_price m 46,951 22,454 6ms 28ms 256ms 2.5s 0 transport_latency_assumed last_trade_price n 46,649 166 52ms 1.0s 6.5s 26.4s 0 transport_latency_assumed last_trade_price o 47,049 24,355 6ms 25ms 219ms 1.3s 0 transport_latency_assumed market_resolved h 916 18 20ms 83ms 51.8s 51.9s 0 transport_latency_assumed market_resolved i 916 55 22ms 107ms 31.4s 2.1min 0 transport_latency_assumed market_resolved m 916 397 5ms 22ms 33.3s 45.2s 0 transport_latency_assumed market_resolved n 916 1 46ms 207ms 42.7s 56.0s 0 transport_latency_assumed market_resolved o 916 460 5ms 17ms 33.0s 45.2s 0 transport_latency_assumed new_market h 831 187 155ms 46.2s 2.2min 2.4min 0 transport_latency_assumed new_market i 831 184 89ms 34.4s 1.8min 2.0min 0 transport_latency_assumed new_market m 831 420 56ms 42.2s 1.8min 2.0min 0 transport_latency_assumed new_market n 831 103 197ms 53.3s 1.9min 2.3min 0 transport_latency_assumed new_market o 831 442 85ms 1.1min 2.1min 2.4min 0 transport_latency_assumed price_change h 103,079,656 632,024 18ms 36ms 557ms 53.9s 0 transport_latency_assumed price_change i 103,119,852 519,272 21ms 38ms 591ms 4.0s 0 transport_latency_assumed price_change m 103,260,986 51,155,822 5ms 14ms 122ms 6.9s 0 transport_latency_assumed price_change n 103,178,302 89,960 45ms 79ms 1.6s 30.3s 0 transport_latency_assumed price_change o 103,218,576 50,994,648 5ms 14ms 116ms 8.0s 0 transport_latency_assumed tick_size_change h 2,336 4 18ms 28ms 68ms 156ms 0 transport_latency_assumed tick_size_change i 2,336 4 21ms 34ms 58ms 167ms 0 transport_latency_assumed tick_size_change m 2,336 1,194 5ms 10ms 28ms 67ms 0 transport_latency_assumed tick_size_change n 2,336 not meas. 44ms 54ms 98ms 340ms 0 transport_latency_assumed tick_size_change o 2,336 1,134 5ms 12ms 38ms 73ms 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-08/21/2026-10-08T21.parquet sha256sum 2026-10-08T21.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.