Hour audit: 2026-09-20T00
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-20T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T00:00:00.000026112+00:00 · last event 2026-09-20T00:59:59.999210361+00:00
VOLUME 147,839,135 rows · 1,643,814,854 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 145,505,889 · h: 145,456,980 · g: 123,838,607 · c: 123,664,715 · f: 51,420,647 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,427,930 (1.64%) · h: 26,931,926 (18.22%) · g: 888,791 (0.60%) · c: 116,619,552 (78.88%) · f: 970,936 (0.66%) (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 147,839,135 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7398595ccbb67d2049f39c44a010e2f3cacfa3b544095c6a5fda6cc56cba9a7d
the corpus checksum ledger names this file with the same digest
joined 147,854,779 to merged 147,839,135, minus 15,644 (minus 0.0106%)
boundary drops 15,644 · 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-20T11:05:05Z 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 18,376,890 206,821,451 0-70 fed8b1c45aeb28ffba7902f501f0cd0fc720b90e333131ff3ff700657726e704 book 2,621,691 109,332,989 71-81 b0162180a4dd8f32f96e7d8b8b445dc6c3c5f818bd9c454070f88c0af4cc86ef last_trade_price 56,746 3,340,896 82-82 daffc03aaa0a401ffc81989019f4c60913b782a8d3366178c69756c098ee8ee1 market_resolved 6,025 632,715 83-83 60028fd183c38edbcad022ba02ddd5bf80bec7aaac15487a978a2dfca7ac0194 new_market 911 87,475 84-84 3c25b750f16e8680332cea0f9741d585a914861e74df88cf39c62c13a32712ff price_change 126,768,536 1,321,611,502 85-568 5f7fddd46c8a306cc35c3308954da9ca713c32792f94c5320040ae301fad5c04 tick_size_change 8,336 307,714 569-569 9eb3b2922cab172c918483b0486f470c885d76087fa07ed30c99330505208b86 EVENT MIX count share price_change 126,768,536 85.75% best_bid_ask 18,376,890 12.43% book 2,621,691 1.77% last_trade_price 56,746 0.04% tick_size_change 8,336 <0.01% market_resolved 6,025 <0.01% new_market 911 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 18,377,286 18,376,890 396 20,977 FULL book 2,634,248 2,621,691 12,557 147,340 FULL last_trade_price 56,746 56,746 0 1,965 FULL market_resolved 6,026 6,025 1 1,261 FULL new_market 911 911 0 165 FULL price_change 126,771,226 126,768,536 2,690 17,193 FULL tick_size_change 8,336 8,336 0 1,429 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 15,514,896 14,769,764 5ms 12ms 97ms 3.8s 0 transport_latency_assumed best_bid_ask e 18,372,618 276,386 42ms 51ms 143ms 4.9s 0 transport_latency_assumed best_bid_ask f 6,399,059 20,236 48ms 62ms 217ms 4.2s 0 transport_latency_assumed best_bid_ask g 15,520,922 4,962 81ms 97ms 264ms 11.2s 0 transport_latency_assumed best_bid_ask h 18,374,878 3,305,542 18ms 33ms 113ms 10.2s 0 transport_latency_assumed book c 1,584,151 749,104 6.8min 1.4d 39.2d 113.1d 0 book_staleness book e 345,782 121,773 1.1min 10.1h 28.5d 113.1d 0 book_staleness book f 1,189,334 794,327 5.9min 1.3d 39.2d 113.1d 0 book_staleness book g 1,654,031 837,870 5.8min 1.4d 39.2d 113.1d 0 book_staleness book h 281,716 118,617 27.1s 7.3h 28.4d 113.1d 0 book_staleness last_trade_price c 47,161 43,515 6ms 25ms 253ms 1.4s 0 transport_latency_assumed last_trade_price e 56,490 1,621 44ms 99ms 588ms 5.0s 0 transport_latency_assumed last_trade_price f 20,273 103 50ms 116ms 924ms 4.2s 0 transport_latency_assumed last_trade_price g 48,113 109 84ms 193ms 2.2s 11.2s 0 transport_latency_assumed last_trade_price h 56,625 11,398 19ms 50ms 266ms 10.0s 0 transport_latency_assumed market_resolved c 4,048 3,280 6ms 6.8min 11.1min 11.6min 0 transport_latency_assumed market_resolved e 3,710 41 72ms 140ms 292ms 1.2min 0 transport_latency_assumed market_resolved f 3,994 1,469 395ms 11.6min 15.4min 16.1min 0 transport_latency_assumed market_resolved g 4,472 514 207ms 8.8min 13.3min 14.0min 0 transport_latency_assumed market_resolved h 3,710 721 34ms 66ms 143ms 5.5s 0 transport_latency_assumed new_market c 558 369 74ms 28.9s 2.3h 4.7h 0 transport_latency_assumed new_market e 542 110 136ms 13.3s 38.7s 54.8min 0 transport_latency_assumed new_market f 489 139 250ms 6.9min 3.2h 4.6h 0 transport_latency_assumed new_market g 598 98 270ms 4.8min 3.2h 5.5h 0 transport_latency_assumed new_market h 542 195 120ms 17.9s 51.8s 1.3h 0 transport_latency_assumed price_change c 106,507,201 101,047,037 5ms 14ms 107ms 4.1s 0 transport_latency_assumed price_change e 126,718,411 2,027,938 42ms 55ms 181ms 6.0s 0 transport_latency_assumed price_change f 43,804,590 154,655 48ms 68ms 262ms 5.1s 0 transport_latency_assumed price_change g 106,603,051 45,238 81ms 101ms 333ms 11.2s 0 transport_latency_assumed price_change h 126,731,173 23,493,668 18ms 35ms 131ms 10.7s 0 transport_latency_assumed tick_size_change c 6,700 6,483 5ms 10ms 57ms 346ms 0 transport_latency_assumed tick_size_change e 8,336 61 42ms 49ms 96ms 340ms 0 transport_latency_assumed tick_size_change f 2,908 7 48ms 53ms 126ms 395ms 0 transport_latency_assumed tick_size_change g 7,420 not meas. 80ms 93ms 217ms 1.2s 0 transport_latency_assumed tick_size_change h 8,336 1,785 18ms 31ms 82ms 337ms 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-20/00/2026-09-20T00.parquet sha256sum 2026-09-20T00.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.