Hour audit: 2026-09-11T03
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-09-11T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T03:00:00.000012154+00:00 · last event 2026-09-11T03:59:59.999917914+00:00
VOLUME 110,660,744 rows · 1,147,795,026 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 110,055,378 · f: 110,037,418 · e: 110,008,897 · c: 105,427,719 · g: 105,266,712 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,834,707 (7.08%) · f: 147,260 (0.13%) · e: 855,931 (0.77%) · c: 101,622,325 (91.83%) · g: 200,521 (0.18%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,660,744 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4a960c2e8e74d714a738a744952c5f19e261c2e38ae83c050d17a8909a603df8
the corpus checksum ledger names this file with the same digest
joined 110,664,803 to merged 110,660,744, minus 4,059 (minus 0.0037%)
boundary drops 4,059 · 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-11T05:01:25Z as cefgh
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 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 11,017,644 121,177,878 0-42 4ef90625b1ff5a85f42fdc44483becbfe724a1949552605de17c55f3b4026bb5 book 729,260 66,866,257 43-45 f88b2a5d918da5855e29d99d028f7bc70e0ab79010636ea828490db5df549fc5 last_trade_price 62,001 3,404,201 46-46 4e24ed5e83d1b428073ca78cc5ce40fbd1bbf4473dbf988491acfba638a4d8c3 market_resolved 1,395 219,326 47-47 5435c2b79bee7c21d5f7818fe768489dc81fc8f0a9460eb26abcb3911ffac5f8 new_market 866 90,312 48-48 552511a24e93970dc2daf74e19c556a9681e4e077a8d77a20ed9fa4853fc0716 price_change 98,846,774 954,672,081 49-426 7f5a8ccda9a3eef1b5545515b8b213ed6f69e0b729fbd9ac8e3cde3d454f8740 tick_size_change 2,804 102,350 427-427 ce584ae38d36e0a216cbfebc1811377e53afdee432e05e78d7678b1be4c0e0a6 EVENT MIX count share price_change 98,846,774 89.32% best_bid_ask 11,017,644 9.96% book 729,260 0.66% last_trade_price 62,001 0.06% tick_size_change 2,804 <0.01% market_resolved 1,395 <0.01% new_market 866 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,017,856 11,017,644 212 1,187 FULL book 729,320 729,260 60 201,976 FULL last_trade_price 62,002 62,001 1 176 FULL market_resolved 1,395 1,395 0 12 FULL new_market 866 866 0 0 FULL price_change 98,850,560 98,846,774 3,786 2,070 FULL tick_size_change 2,804 2,804 0 48 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,497,828 10,137,451 5ms 9ms 82ms 3.9s 0 transport_latency_assumed best_bid_ask e 11,014,846 84,540 38ms 44ms 129ms 6.2s 0 transport_latency_assumed best_bid_ask f 11,016,360 13,797 45ms 53ms 158ms 5.6s 0 transport_latency_assumed best_bid_ask g 10,475,967 1,591 77ms 94ms 265ms 11.8s 0 transport_latency_assumed best_bid_ask h 11,016,908 780,265 17ms 24ms 112ms 10.2s 0 transport_latency_assumed book c 535,548 528,190 3.2min 20.6h 26.5d 104.2d 0 book_staleness book e 135,105 4,620 40ms 117ms 11.7min 41.9d 0 book_staleness book f 133,451 956 47ms 97ms 2.7s 40.6d 0 book_staleness book g 545,042 182,691 3.0min 20.0h 26.4d 104.2d 0 book_staleness book h 133,462 12,803 20ms 49ms 2.2s 4.1d 0 book_staleness last_trade_price c 57,819 55,315 10ms 40ms 192ms 5.0s 0 transport_latency_assumed last_trade_price e 61,609 764 45ms 102ms 1.2s 6.2s 0 transport_latency_assumed last_trade_price f 61,878 159 52ms 106ms 466ms 5.6s 0 transport_latency_assumed last_trade_price g 59,327 35 89ms 193ms 1.8s 11.7s 0 transport_latency_assumed last_trade_price h 61,861 5,728 23ms 63ms 306ms 6.3s 0 transport_latency_assumed market_resolved c 1,313 1,260 5ms 11ms 3.8min 5.3min 0 transport_latency_assumed market_resolved e 1,325 1 40ms 114ms 51.0s 1.0min 0 transport_latency_assumed market_resolved f 1,325 2 46ms 123ms 49.8s 58.4s 0 transport_latency_assumed market_resolved g 1,325 25 83ms 242ms 4.3min 4.3min 0 transport_latency_assumed market_resolved h 1,325 107 18ms 50ms 1.0min 1.0min 0 transport_latency_assumed new_market c 590 313 85ms 15.6s 1.6min 2.1min 0 transport_latency_assumed new_market e 590 133 154ms 35.2s 1.7min 2.0min 0 transport_latency_assumed new_market f 590 54 166ms 40.8s 1.7min 2.1min 0 transport_latency_assumed new_market g 590 79 232ms 36.0s 1.6min 2.1min 0 transport_latency_assumed new_market h 590 287 113ms 20.7s 1.6min 2.1min 0 transport_latency_assumed price_change c 94,331,897 90,897,137 5ms 10ms 96ms 4.2s 0 transport_latency_assumed price_change e 98,792,618 765,853 39ms 46ms 169ms 6.2s 0 transport_latency_assumed price_change f 98,821,010 132,292 45ms 56ms 198ms 5.6s 0 transport_latency_assumed price_change g 94,181,769 16,100 77ms 98ms 327ms 12.9s 0 transport_latency_assumed price_change h 98,838,428 7,035,392 17ms 27ms 135ms 10.3s 0 transport_latency_assumed tick_size_change c 2,724 2,659 5ms 7ms 38ms 73ms 0 transport_latency_assumed tick_size_change e 2,804 20 38ms 42ms 97ms 695ms 0 transport_latency_assumed tick_size_change f 2,804 not meas. 45ms 50ms 92ms 246ms 0 transport_latency_assumed tick_size_change g 2,692 not meas. 76ms 91ms 136ms 200ms 0 transport_latency_assumed tick_size_change h 2,804 125 17ms 22ms 55ms 198ms 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-09-11/03/2026-09-11T03.parquet sha256sum 2026-09-11T03.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.