Hour audit: 2026-09-18T23
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-18T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T23:00:00.000541076+00:00 · last event 2026-09-18T23:59:59.999981022+00:00
VOLUME 115,586,935 rows · 1,194,950,638 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 115,257,370 · e: 115,187,946 · h: 115,173,384 · f: 115,161,409 · g: 115,077,824 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 109,045,825 (94.34%) · e: 585,937 (0.51%) · h: 5,522,047 (4.78%) · f: 291,180 (0.25%) · g: 141,946 (0.12%) (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 115,586,935 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5162dc325ddee3117c45202c584f0adb650a3d1ea539cf68f664859ac900a142
the corpus checksum ledger names this file with the same digest
joined 115,591,007 to merged 115,586,935, minus 4,072 (minus 0.0035%)
boundary drops 4,072 · 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-19T03:15: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 12,774,468 140,026,559 0-48 63d66fbe4c8d027b392907696403e6bb191c8adcb0086cd1238f4c14e15aab8f book 539,814 48,924,567 49-51 f4ad6c713da78cdf056b39eb955b8e97ab45bd67138a77a6e9773172de33f301 last_trade_price 54,229 3,052,918 52-52 4ce10320eee522582dcaf1422af1216e4e040a8430c50d1fe4ae83d461a423e0 market_resolved 1,378 216,610 53-53 6ef5a43341e6bd500012d1e836d872294c09d82669f738324835181e401fa5e1 new_market 1,536 167,825 54-54 d97b4d9ce93e4ea2658c24abaae8712e4794e6bc942868364edf5b0d09c682f4 price_change 102,212,122 1,001,122,928 55-444 7892501cd5cd614461ae9df0ef775c2fe91d68cad1a97c6f0da5461e9caef3de tick_size_change 3,388 124,401 445-445 e1ca726217a60d87761843cca2d245cbca3f971d8a44a995e61f13c26eabfd53 EVENT MIX count share price_change 102,212,122 88.43% best_bid_ask 12,774,468 11.05% book 539,814 0.47% last_trade_price 54,229 0.05% tick_size_change 3,388 <0.01% new_market 1,536 <0.01% market_resolved 1,378 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,774,788 12,774,468 320 228 FULL book 540,156 539,814 342 158,947 FULL last_trade_price 54,230 54,229 1 1 FULL market_resolved 1,379 1,378 1 3 FULL new_market 1,536 1,536 0 0 FULL price_change 102,215,530 102,212,122 3,408 57 FULL tick_size_change 3,388 3,388 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,772,796 12,123,428 5ms 12ms 125ms 6.8s 0 transport_latency_assumed best_bid_ask e 12,770,817 53,067 40ms 51ms 189ms 10.3s 0 transport_latency_assumed best_bid_ask f 12,770,837 22,371 47ms 60ms 225ms 9.8s 0 transport_latency_assumed best_bid_ask g 12,768,991 4,292 78ms 98ms 353ms 10.4s 0 transport_latency_assumed best_bid_ask h 12,770,847 571,310 18ms 27ms 148ms 40.9s 0 transport_latency_assumed book c 237,641 198,281 3.5s 7.7h 27.4d 112.1d 0 book_staleness book e 214,952 78,250 443ms 7.6h 27.4d 112.1d 0 book_staleness book f 210,012 71,812 382ms 7.6h 24.2d 112.1d 0 book_staleness book g 242,479 99,648 9.5s 7.7h 27.4d 110.5d 0 book_staleness book h 224,244 91,823 332ms 7.7h 27.4d 93.6d 0 book_staleness last_trade_price c 54,086 50,582 10ms 51ms 273ms 5.2s 0 transport_latency_assumed last_trade_price e 54,058 328 51ms 221ms 3.5s 10.4s 0 transport_latency_assumed last_trade_price f 53,917 129 60ms 267ms 2.8s 5.7s 0 transport_latency_assumed last_trade_price g 53,574 80 91ms 304ms 5.6s 10.2s 0 transport_latency_assumed last_trade_price h 53,833 3,110 24ms 79ms 445ms 27.4s 0 transport_latency_assumed market_resolved c 1,339 1,264 5ms 16ms 51.7s 1.0min 0 transport_latency_assumed market_resolved e 1,339 38 42ms 208ms 53.3s 59.1s 0 transport_latency_assumed market_resolved f 1,339 1 49ms 211ms 52.3s 1.0min 0 transport_latency_assumed market_resolved g 1,340 29 83ms 321ms 799ms 1.2s 0 transport_latency_assumed market_resolved h 1,340 46 19ms 84ms 53.2s 59.2s 0 transport_latency_assumed new_market c 1,086 584 97ms 15.1s 57.0s 26.9min 0 transport_latency_assumed new_market e 1,086 244 131ms 17.0s 1.0min 20.3min 0 transport_latency_assumed new_market f 1,086 161 196ms 19.8s 1.0min 29.5min 0 transport_latency_assumed new_market g 1,086 95 221ms 17.3s 54.3s 15.8min 0 transport_latency_assumed new_market h 1,086 452 113ms 14.4s 53.8s 26.1min 0 transport_latency_assumed price_change c 102,187,034 96,668,434 5ms 14ms 137ms 6.8s 0 transport_latency_assumed price_change e 102,142,306 453,996 41ms 60ms 348ms 12.4s 0 transport_latency_assumed price_change f 102,120,830 196,698 47ms 70ms 395ms 11.0s 0 transport_latency_assumed price_change g 102,006,966 37,802 79ms 113ms 605ms 10.6s 0 transport_latency_assumed price_change h 102,118,650 4,855,192 18ms 31ms 188ms 45.6s 0 transport_latency_assumed tick_size_change c 3,388 3,252 5ms 12ms 69ms 312ms 0 transport_latency_assumed tick_size_change e 3,388 14 41ms 51ms 118ms 294ms 0 transport_latency_assumed tick_size_change f 3,388 8 47ms 55ms 120ms 365ms 0 transport_latency_assumed tick_size_change g 3,388 not meas. 78ms 92ms 195ms 338ms 0 transport_latency_assumed tick_size_change h 3,384 114 18ms 30ms 98ms 662ms 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-18/23/2026-09-18T23.parquet sha256sum 2026-09-18T23.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.