Hour audit: 2026-09-03T13
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-03T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T13:00:00.014675733+00:00 · last event 2026-09-03T13:59:59.999994481+00:00
VOLUME 57,699,611 rows · 622,334,705 bytes (593.50 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 57,247,607 · h: 56,546,210 · e: 54,786,173 · b: 49,394,553 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 224,556 (0.39%) · h: 2,601,632 (4.51%) · e: 54,784,811 (94.95%) · b: 88,612 (0.15%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 57,699,611 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 c40038ccd1d2b2dc89180ed023cc9ed2241227db15e45d06d7997b75f959c490
the corpus checksum ledger names this file with the same digest
joined 57,701,621 to merged 57,699,611, minus 2,010 (minus 0.0035%)
boundary drops 2,010 · 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-03T14:46:10Z as bceh
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: Venue paused trading for about twenty minutes, 2026-09-03T13:07Z to 2026-09-03T13:26ZThe 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 5,834,866 76,925,722 0-22 d033c1a60123e40ef9bf16f0e51dca3cb1065296c51526fda4a1e225a2d841f5 book 325,980 29,839,438 23-24 423f2b65ca88439b987e83dc728751775e66b170f087f27ecdc2515f318009ff last_trade_price 51,901 2,979,047 25-25 d37eac44348898fb0a902bb6a1f6166347897ef1301a98c90a844774c28fff82 market_resolved 3,071 498,326 26-26 d3c665c69be1d78f5a95c34709ded4f1404aa89a70e45962eaa259ad68553da1 new_market 1,113 121,239 27-27 a9f5f78fd94e4d26ba46c1e480df5244df054f751d4ad45f4b3ade9ca95ff537 price_change 51,478,020 511,132,260 28-224 0b16677fc7b6794686b2f1a97e79bf96a67d06e13a1eee0c29996601066dc521 tick_size_change 4,660 171,615 225-225 fb106ce7a7f8e389042a0d9b38e01553dac39050f70bb33d56f6c38bcd5f6121 EVENT MIX count share price_change 51,478,020 89.22% best_bid_ask 5,834,866 10.11% book 325,980 0.56% last_trade_price 51,901 0.09% tick_size_change 4,660 <0.01% market_resolved 3,071 <0.01% new_market 1,113 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 5,834,974 5,834,866 108 112 FULL book 325,984 325,980 4 83,083 FULL last_trade_price 51,901 51,901 0 3 FULL market_resolved 3,071 3,071 0 1 FULL new_market 1,113 1,113 0 0 FULL price_change 51,479,918 51,478,020 1,898 54,077 FULL tick_size_change 4,660 4,660 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 5,811,860 36 52ms 114ms 1.7s 35.8s 0 transport_latency_assumed best_bid_ask c 5,834,656 3,594 4ms 9ms 195ms 6.8s 0 transport_latency_assumed best_bid_ask e 5,799,273 5,799,193 40ms 134ms 5.0s 39.7s 0 transport_latency_assumed best_bid_ask h 5,830,365 32,043 20ms 32ms 277ms 17.4s 0 transport_latency_assumed book b 199,667 87,241 10.5s 38.2min 26.0d 96.6d 0 book_staleness book c 127,463 20,452 9ms 1.3min 1.6d 78.1d 0 book_staleness book e 124,201 124,199 228ms 5.1min 12.0d 78.1d 0 book_staleness book h 189,072 94,088 394ms 17.7min 25.9d 96.6d 0 book_staleness last_trade_price b 45,751 3 102ms 4.7s 18.4s 34.8s 0 transport_latency_assumed last_trade_price c 51,879 1,029 11ms 49ms 286ms 4.6s 0 transport_latency_assumed last_trade_price e 44,837 44,837 94ms 4.7s 21.1s 39.7s 0 transport_latency_assumed last_trade_price h 50,762 6,032 33ms 401ms 7.0s 17.4s 0 transport_latency_assumed market_resolved b 3,068 not meas. 55ms 191ms 639ms 4.0s 0 transport_latency_assumed market_resolved c 3,068 not meas. 4ms 7ms 163ms 59.5s 0 transport_latency_assumed market_resolved e 3,067 3,067 42ms 179ms 713ms 1.0min 0 transport_latency_assumed market_resolved h 3,068 4 21ms 55ms 277ms 3.8s 0 transport_latency_assumed new_market b 787 76 222ms 11.9s 38.2s 2.6min 0 transport_latency_assumed new_market c 787 135 45ms 18.6s 35.2s 4.8min 0 transport_latency_assumed new_market e 787 787 213ms 16.4s 33.8s 1.4min 0 transport_latency_assumed new_market h 787 115 101ms 11.4s 35.9s 1.1min 0 transport_latency_assumed price_change b 43,328,760 1,256 53ms 207ms 9.7s 35.8s 0 transport_latency_assumed price_change c 51,225,094 199,346 5ms 11ms 278ms 7.0s 0 transport_latency_assumed price_change e 48,809,348 48,808,068 41ms 244ms 10.0s 39.8s 0 transport_latency_assumed price_change h 50,467,496 2,469,350 20ms 45ms 1.1s 17.4s 0 transport_latency_assumed tick_size_change b 4,660 not meas. 53ms 76ms 293ms 689ms 0 transport_latency_assumed tick_size_change c 4,660 not meas. 5ms 8ms 134ms 305ms 0 transport_latency_assumed tick_size_change e 4,660 4,660 41ms 121ms 365ms 12.6s 0 transport_latency_assumed tick_size_change h 4,660 not meas. 20ms 27ms 117ms 2.0s 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-03/13/2026-09-03T13.parquet sha256sum 2026-09-03T13.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.