Hour audit: 2026-09-03T17
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-03T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T17:00:00.029671410+00:00 · last event 2026-09-03T17:59:59.121885810+00:00
VOLUME 9,048,653 rows · 141,724,577 bytes (135.16 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 8,755,011 · e: 8,740,657 · h: 8,724,651 · b: 8,650,623 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 100,972 (1.12%) · e: 8,739,070 (96.58%) · h: 151,597 (1.68%) · b: 57,014 (0.63%) (rows of the merged file that came from it; these partition it)
7 product-machine pairs publish no supplied count; the figures above still sum to the file's 9,048,653 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 2229fe2aaed6b18e3dbe7d10627b6d12e93c7bdc73fa20a5d7d301bccd9230ee
the corpus checksum ledger names this file with the same digest
joined 9,050,546 to merged 9,048,653, minus 1,893 (minus 0.0209%)
boundary drops 1,893 · 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-03T18:37:40Z 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, then twice more in cancel-only mode, 2026-09-03T17:06Z to 2026-09-03T21:35ZThe 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 669,134 9,285,555 0-2 473b99357eff7b017316908c1ac39dedd360e4fdfe958bf168900282de7a41b6 book 592,020 48,573,181 3-5 6f9d9b3fb6e35a785d0f4a182af7e13ab50b2f8d383421309f98c57c22760bcd last_trade_price 7,983 478,195 6-6 516e3cfedf4a7369efa38f8396804f2cdee1c09a32e256aa1cfb00ddb0a7f38c market_resolved 905 140,681 7-7 5e211aa3cb12a2c32d4551581379464fca4dd454452f0e7c4b3ce27c4a553f61 new_market 944 105,265 8-8 4d1c1e6ad00a7f50ac7cfafcc1294c38210fca4d000618cb11e113e43f42153a price_change 7,777,103 83,000,945 9-38 362ba7726ba25b556bacc1ece4a925acec62da12fd1179af0222286495f0f395 tick_size_change 564 21,400 39-39 a994b52f738371fb4be622796d86cf751cf859c9d20104a554a44c40677d9d34 EVENT MIX count share price_change 7,777,103 85.95% best_bid_ask 669,134 7.39% book 592,020 6.54% last_trade_price 7,983 0.09% new_market 944 0.01% market_resolved 905 0.01% tick_size_change 564 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 669,182 669,134 48 10 FULL book 592,076 592,020 56 161,549 FULL last_trade_price 7,983 7,983 0 0 FULL market_resolved 905 905 0 0 FULL new_market 944 944 0 0 FULL price_change 7,778,892 7,777,103 1,789 23 FULL tick_size_change 564 564 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 667,068 not meas. 51ms 82ms 907ms 19.4s 0 transport_latency_assumed best_bid_ask c 669,126 36 9ms 13ms 61ms 2.5s 0 transport_latency_assumed best_bid_ask e 668,740 668,708 41ms 99ms 2.3s 13.0s 0 transport_latency_assumed best_bid_ask h 669,042 390 18ms 27ms 120ms 1.9s 0 transport_latency_assumed book b 258,203 56,873 39.8min 5.8h 32.2d 96.8d 0 book_staleness book c 298,782 100,240 39.0min 5.7h 32.2d 96.8d 0 book_staleness book e 297,176 297,150 39.1min 6.3h 32.2d 96.8d 0 book_staleness book h 270,394 137,757 40.2min 5.7h 32.2d 96.8d 0 book_staleness last_trade_price b 7,498 not meas. 106ms 5.0s 14.1s 19.4s 0 transport_latency_assumed last_trade_price c 7,981 2 14ms 45ms 171ms 4.9s 0 transport_latency_assumed last_trade_price e 7,913 7,913 105ms 6.7s 12.3s 13.0s 0 transport_latency_assumed last_trade_price h 7,951 68 28ms 182ms 1.3s 4.9s 0 transport_latency_assumed market_resolved b 879 not meas. 50ms 133ms 555ms 854ms 0 transport_latency_assumed market_resolved c 879 26 7ms 9ms 34ms 663ms 0 transport_latency_assumed market_resolved e 879 879 40ms 189ms 56.9s 59.1s 0 transport_latency_assumed market_resolved h 879 not meas. 19ms 40ms 56.9s 58.8s 0 transport_latency_assumed new_market b 689 95 232ms 12.9s 42.4s 2.3min 0 transport_latency_assumed new_market c 689 34 63ms 12.0s 44.3s 1.1min 0 transport_latency_assumed new_market e 689 689 218ms 13.0s 43.9s 1.7min 0 transport_latency_assumed new_market h 689 126 119ms 11.4s 26.9s 1.5min 0 transport_latency_assumed price_change b 7,715,722 46 52ms 164ms 6.1s 19.5s 0 transport_latency_assumed price_change c 7,776,990 634 9ms 14ms 149ms 4.6s 0 transport_latency_assumed price_change e 7,764,696 7,763,167 42ms 195ms 8.4s 13.0s 0 transport_latency_assumed price_change h 7,775,132 13,256 19ms 40ms 285ms 4.1s 0 transport_latency_assumed tick_size_change b 564 not meas. 50ms 61ms 115ms 199ms 0 transport_latency_assumed tick_size_change c 564 not meas. 9ms 11ms 14ms 20ms 0 transport_latency_assumed tick_size_change e 564 564 41ms 45ms 123ms 169ms 0 transport_latency_assumed tick_size_change h 564 not meas. 18ms 21ms 45ms 72ms 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/17/2026-09-03T17.parquet sha256sum 2026-09-03T17.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.