Hour audit: 2026-09-19T19
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-19T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T19:00:00.000041937+00:00 · last event 2026-09-19T19:59:59.943632101+00:00
VOLUME 52,580,510 rows · 577,800,764 bytes (551.03 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 52,444,592 · f: 52,436,703 · g: 52,422,267 · c: 52,403,927 · e: 52,387,985 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,810,163 (5.34%) · f: 379,941 (0.72%) · g: 135,058 (0.26%) · c: 48,731,622 (92.68%) · e: 523,726 (1.00%) (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 52,580,510 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 059a7ae41a7455f02a4ac995ea382543689191587685e2ce1a99f967cdd0d1f0
the corpus checksum ledger names this file with the same digest
joined 52,582,642 to merged 52,580,510, minus 2,132 (minus 0.0041%)
boundary drops 2,132 · 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-19T20:46:01Z 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 an incident recorded by the venue intersects this hour: Trading paused by degraded block production on Polygon, 2026-09-19T19:38Z to 2026-09-19T20:20ZThe 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 6,735,156 84,863,572 0-25 06fd37aa50932f37a69688873ee3e13f2183f1ba20754d9cf48b4e27fbeae276 book 243,736 19,275,243 26-26 1bc213199d70c608002a99dcc09d1f71491689310baec4193bedb9cb1c21f32a last_trade_price 20,635 1,359,646 27-27 c53fdee8d306e2bcfa1c4865a47c8191480daa0bfb6590c101c8fdc08d27754e market_resolved 3,510 563,812 28-28 b196eea8518e2e8031f04b1876052959423351220ef15e29d01953297826b669 new_market 3,800 391,118 29-29 1d8f535cd582889dedcccd48d2468a2986b25c2590bc32c1892d37f9b4e1f10a price_change 45,565,089 470,430,808 30-203 fbc046b9cf3836907a32d2b6badd5fb762dd08076007c9c7199eea88bcc3de88 tick_size_change 8,584 311,045 204-204 736125b12c0d99a27df5a479002f1b081bf121273d7b949ffc6f8dc0305dc483 EVENT MIX count share price_change 45,565,089 86.66% best_bid_ask 6,735,156 12.81% book 243,736 0.46% last_trade_price 20,635 0.04% tick_size_change 8,584 0.02% new_market 3,800 <0.01% market_resolved 3,510 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,735,486 6,735,156 330 149 FULL book 243,770 243,736 34 62,163 FULL last_trade_price 20,637 20,635 2 1 FULL market_resolved 3,510 3,510 0 2 FULL new_market 3,800 3,800 0 14 FULL price_change 45,566,855 45,565,089 1,766 103 FULL tick_size_change 8,584 8,584 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,734,440 6,288,428 5ms 17ms 324ms 10.4s 0 transport_latency_assumed best_bid_ask e 6,733,934 65,313 41ms 57ms 438ms 17.7s 0 transport_latency_assumed best_bid_ask f 6,734,394 40,833 45ms 62ms 352ms 16.1s 0 transport_latency_assumed best_bid_ask g 6,733,652 9,488 79ms 108ms 531ms 20.4s 0 transport_latency_assumed best_bid_ask h 6,734,376 331,094 19ms 33ms 1.0s 1.0min 0 transport_latency_assumed book c 77,552 68,765 8ms 11.2min 12.4d 94.4d 0 book_staleness book e 77,203 12,298 45ms 11.1min 11.0d 112.9d 0 book_staleness book f 111,097 43,787 180ms 41.5min 25.0d 94.4d 0 book_staleness book g 130,018 60,775 13.9s 3.8h 28.2d 105.2d 0 book_staleness book h 121,405 58,111 1.7s 2.6h 28.2d 94.4d 0 book_staleness last_trade_price c 20,582 18,572 6ms 50ms 497ms 2.2s 0 transport_latency_assumed last_trade_price e 20,527 275 44ms 232ms 2.3s 17.7s 0 transport_latency_assumed last_trade_price f 20,633 152 48ms 197ms 3.1s 16.1s 0 transport_latency_assumed last_trade_price g 20,456 43 83ms 390ms 5.0s 20.5s 0 transport_latency_assumed last_trade_price h 20,591 1,593 20ms 94ms 2.2s 42.5s 0 transport_latency_assumed market_resolved c 3,506 3,387 5ms 11ms 275ms 754ms 0 transport_latency_assumed market_resolved e 3,505 27 110ms 201ms 430ms 49.0s 0 transport_latency_assumed market_resolved f 3,505 10 112ms 207ms 402ms 1.0min 0 transport_latency_assumed market_resolved g 3,504 1 192ms 364ms 698ms 4.0s 0 transport_latency_assumed market_resolved h 3,506 85 35ms 76ms 497ms 33.0s 0 transport_latency_assumed new_market c 2,406 1,458 138ms 35.0s 15.4min 23.4min 0 transport_latency_assumed new_market e 2,420 789 188ms 29.7s 16.9min 1.4h 0 transport_latency_assumed new_market f 2,406 478 177ms 25.0s 16.6min 18.2min 0 transport_latency_assumed new_market g 2,406 275 252ms 26.4s 16.8min 22.3min 0 transport_latency_assumed new_market h 2,406 800 187ms 26.4s 8.7min 18.2min 0 transport_latency_assumed price_change c 45,556,857 42,342,684 5ms 21ms 345ms 10.4s 0 transport_latency_assumed price_change e 45,541,812 445,016 41ms 74ms 557ms 17.7s 0 transport_latency_assumed price_change f 45,556,084 294,677 46ms 76ms 426ms 16.1s 0 transport_latency_assumed price_change g 45,523,647 64,476 79ms 137ms 758ms 20.5s 0 transport_latency_assumed price_change h 45,553,724 2,418,236 19ms 40ms 994ms 1.0min 0 transport_latency_assumed tick_size_change c 8,584 8,328 5ms 9ms 95ms 229ms 0 transport_latency_assumed tick_size_change e 8,584 8 40ms 44ms 73ms 422ms 0 transport_latency_assumed tick_size_change f 8,584 4 45ms 49ms 95ms 424ms 0 transport_latency_assumed tick_size_change g 8,584 not meas. 78ms 90ms 114ms 1.8s 0 transport_latency_assumed tick_size_change h 8,584 244 18ms 23ms 61ms 6.1s 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-19/19/2026-09-19T19.parquet sha256sum 2026-09-19T19.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.