Hour audit: 2026-09-20T17
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-20T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T17:00:00.000000858+00:00 · last event 2026-09-20T17:59:59.999996908+00:00
VOLUME 164,697,884 rows · 1,911,180,748 bytes (1.78 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 154,237,554 · e: 137,413,570 · g: 125,311,738 · f: 113,899,477 · c: 81,531,305 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 77,950,787 (47.33%) · e: 7,709,176 (4.68%) · g: 1,036,667 (0.63%) · f: 3,089,995 (1.88%) · c: 74,911,259 (45.48%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 16878627fcfefaf7b585605e9d451059b942d3118c89e93f915fd74cb68e85c8
the corpus checksum ledger names this file with the same digest
joined 164,709,321 to merged 164,697,884, minus 11,437 (minus 0.0069%)
boundary drops 11,437 · 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-20T19:42:17Z 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 16,140,047 192,283,116 0-61 cdfe9772f06d61295a80d0b22116294f5c2b1079ba5740df71e02d78d774107e book 5,943,606 178,330,931 62-84 fe16a7d3a5f12a6719b14f654183b25cd1787ded9bb5d0a00b699828bc4a24b2 last_trade_price 76,630 4,443,634 85-85 f0fd17b6a8df668fedd3302b90037e355f7fffd286003413c654db3b3124b5ac market_resolved 20,382 692,622 86-86 6b20f75173cfe013112e1f7ecf0dd0c2181401179f891a493762a8be1bd2d18d new_market 18,804 525,282 87-87 e9b8ccb20477d2f73d0ea918b9d546e6f2f65e29cd357283cb971e0d2a58393c price_change 142,489,447 1,532,712,140 88-631 2444c1152310d75155fae12cdda38db5c8af39e9f59aa31ecd35cf626b15b702 tick_size_change 8,968 326,296 632-632 9ba29a40735d744eb098521accd36edd1a22b7c9f008a4812336f674ea002637 EVENT MIX count share price_change 142,489,447 86.52% best_bid_ask 16,140,047 9.80% book 5,943,606 3.61% last_trade_price 76,630 0.05% market_resolved 20,382 0.01% new_market 18,804 0.01% tick_size_change 8,968 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 16,140,246 16,140,047 199 14,728 FULL book 5,950,615 5,943,606 7,009 2,563 FULL last_trade_price 76,631 76,630 1 2,131 FULL market_resolved 20,382 20,382 0 701 FULL new_market 18,804 18,804 0 16 FULL price_change 142,493,675 142,489,447 4,228 8,654 FULL tick_size_change 8,968 8,968 0 1,715 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,801,260 7,217,879 6ms 25ms 185ms 7.2s 0 transport_latency_assumed best_bid_ask e 13,875,103 718,123 43ms 73ms 350ms 31.0s 0 transport_latency_assumed best_bid_ask f 11,353,709 220,909 47ms 81ms 356ms 22.9s 0 transport_latency_assumed best_bid_ask g 12,655,928 32,751 81ms 160ms 900ms 27.5s 0 transport_latency_assumed best_bid_ask h 15,670,676 7,950,385 19ms 55ms 288ms 46.0s 0 transport_latency_assumed book c 4,512,977 3,835,328 6.7min 2.1d 43.1d 113.8d 0 book_staleness book e 1,486,664 465,337 4.7min 2.1d 42.8d 113.8d 0 book_staleness book f 2,748,721 829,815 5.7min 2.1d 43.1d 113.8d 0 book_staleness book g 2,153,766 696,228 5.5min 2.1d 43.1d 113.8d 0 book_staleness book h 494,935 116,898 58.4s 1.1d 36.1d 113.8d 0 book_staleness last_trade_price c 37,768 34,705 7ms 34ms 251ms 1.4s 0 transport_latency_assumed last_trade_price e 64,242 2,933 51ms 860ms 12.7s 31.0s 0 transport_latency_assumed last_trade_price f 53,151 1,143 56ms 743ms 7.6s 21.9s 0 transport_latency_assumed last_trade_price g 57,099 230 101ms 1.6s 14.2s 27.6s 0 transport_latency_assumed last_trade_price h 74,124 37,619 21ms 81ms 481ms 36.0s 0 transport_latency_assumed market_resolved c 18,346 15,614 18.5min 38.1min 49.1min 54.9min 0 transport_latency_assumed market_resolved e 5,427 1,188 125ms 14.2min 19.4min 20.0min 0 transport_latency_assumed market_resolved f 4,691 761 152ms 12.3min 18.8min 21.8min 0 transport_latency_assumed market_resolved g 4,100 1,058 203ms 6.3min 10.3min 13.1min 0 transport_latency_assumed market_resolved h 3,757 1,761 34ms 125ms 6.2min 6.5min 0 transport_latency_assumed new_market c 18,343 15,131 14.2min 38.4min 3.4h 19.1h 0 transport_latency_assumed new_market e 4,637 1,605 32.6s 12.1min 2.4h 18.6h 0 transport_latency_assumed new_market f 4,237 709 378ms 9.2min 1.6h 15.4h 0 transport_latency_assumed new_market g 3,446 490 344ms 6.0min 47.1min 12.1h 0 transport_latency_assumed new_market h 3,091 869 134ms 5.2min 6.4min 9.2h 0 transport_latency_assumed price_change c 69,138,179 63,788,439 6ms 28ms 213ms 7.2s 0 transport_latency_assumed price_change e 121,969,977 6,519,832 43ms 95ms 1.7s 31.1s 0 transport_latency_assumed price_change f 99,728,808 2,036,528 47ms 102ms 1.8s 22.9s 0 transport_latency_assumed price_change g 110,430,359 305,906 82ms 218ms 3.9s 28.2s 0 transport_latency_assumed price_change h 137,982,159 69,838,742 19ms 60ms 345ms 50.6s 0 transport_latency_assumed tick_size_change c 4,432 4,163 6ms 18ms 79ms 238ms 0 transport_latency_assumed tick_size_change e 7,520 158 42ms 51ms 179ms 1.0s 0 transport_latency_assumed tick_size_change f 6,160 130 47ms 79ms 241ms 1.7s 0 transport_latency_assumed tick_size_change g 7,040 4 80ms 132ms 516ms 8.1s 0 transport_latency_assumed tick_size_change h 8,812 4,513 19ms 46ms 163ms 5.2s 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/17/2026-09-20T17.parquet sha256sum 2026-09-20T17.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.