Hour audit: 2026-09-03T19
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-03T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T19:00:00.005175561+00:00 · last event 2026-09-03T19:59:59.999929782+00:00
VOLUME 18,988,322 rows · 205,806,684 bytes (196.27 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 14,444,907 · h: 14,364,736 · e: 12,190,667 · b: 9,777,194 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 2,527,247 (13.31%) · h: 4,101,236 (21.60%) · e: 12,190,667 (64.20%) · b: 169,172 (0.89%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 18,988,322 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 4d3e05b80fb36f78cf96b1c5ccc6474540beaebbbef9e9fa6d0e7468572a8a2e
the corpus checksum ledger names this file with the same digest
joined 18,988,322 to merged 18,988,322, no change
boundary drops 0 · 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-03T20:38:32Z 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 2,609,198 38,340,535 0-9 e2116f2852eac37fb5e136bd62f81686795ebe404cbe9a619874b5e023e1c6f8 book 68,605 5,754,199 10-10 1c9df624f72884916ffccf5b1bd65abde2cfc9aa4e651a115863d955acc90db9 last_trade_price 28,636 1,750,639 11-11 1cd717fbf444e28eab74305e56ee91c72bb79cee373279586676dc30ea9256af market_resolved 845 135,596 12-12 d81dc7116303b83eaff0a25b90e5722dfb4fa31c1d59826e46aefae2fcd98925 new_market 3,078 332,534 13-13 a866663e9324bdd67fe40a46f7b75396346d536b9e05f0f8490600e00ecfec9c price_change 16,275,496 159,173,425 14-76 53d0328f82e6ce3d0d1b2cf26c53840c9448fb1e0e02ab481a2b4f2b3f4f83f7 tick_size_change 2,464 89,138 77-77 9c601a2ef6699c005f4207488fdffa2e7e18d1ee8033185f807435e519f1bab5 EVENT MIX count share price_change 16,275,496 85.71% best_bid_ask 2,609,198 13.74% book 68,605 0.36% last_trade_price 28,636 0.15% new_market 3,078 0.02% tick_size_change 2,464 0.01% market_resolved 845 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 2,609,198 2,609,198 0 127 FULL book 68,605 68,605 0 1,830 FULL last_trade_price 28,636 28,636 0 1 FULL market_resolved 845 845 0 0 FULL new_market 3,078 3,078 0 0 FULL price_change 16,275,496 16,275,496 0 91,615 FULL tick_size_change 2,464 2,464 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 2,604,084 not meas. 51ms 125ms 993ms 25.6s 0 transport_latency_assumed best_bid_ask c 2,608,936 532 4ms 9ms 240ms 3.8s 0 transport_latency_assumed best_bid_ask e 2,594,467 2,594,467 43ms 127ms 2.1s 21.2s 0 transport_latency_assumed best_bid_ask h 2,608,474 14,199 18ms 32ms 271ms 1.3min 0 transport_latency_assumed book b 62,400 2,940 131ms 5.8s 3.9h 78.3d 0 book_staleness book c 62,796 879 8ms 219ms 4.0s 78.3d 0 book_staleness book e 60,809 60,809 65ms 4.0s 24.6min 1.5d 0 book_staleness book h 62,446 3,977 39ms 1.1s 10.5s 32.2d 0 book_staleness last_trade_price b 27,284 1 93ms 2.3s 15.4s 24.1s 0 transport_latency_assumed last_trade_price c 28,623 50 10ms 72ms 481ms 4.4s 0 transport_latency_assumed last_trade_price e 26,899 26,899 65ms 2.0s 13.1s 21.5s 0 transport_latency_assumed last_trade_price h 28,582 1,686 30ms 325ms 6.8s 12.2s 0 transport_latency_assumed market_resolved b 815 4 51ms 368ms 48.9s 51.6s 0 transport_latency_assumed market_resolved c 815 23 5ms 43ms 51.9s 1.0min 0 transport_latency_assumed market_resolved e 815 815 43ms 538ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 815 3 19ms 215ms 1.0min 1.0min 0 transport_latency_assumed new_market b 2,117 97 338ms 14.9s 25.9s 1.2min 0 transport_latency_assumed new_market c 2,117 259 106ms 15.4s 26.4s 1.0min 0 transport_latency_assumed new_market e 2,117 2,117 254ms 13.8s 23.9s 1.2min 0 transport_latency_assumed new_market h 2,117 605 192ms 14.0s 23.7s 1.2min 0 transport_latency_assumed price_change b 7,078,030 166,130 55ms 521ms 13.5s 25.9s 0 transport_latency_assumed price_change c 11,739,156 2,525,504 5ms 13ms 290ms 6.9s 0 transport_latency_assumed price_change e 9,503,096 9,503,096 44ms 311ms 9.9s 21.6s 0 transport_latency_assumed price_change h 11,659,838 4,080,766 19ms 55ms 1.2s 1.3min 0 transport_latency_assumed tick_size_change b 2,464 not meas. 50ms 61ms 301ms 477ms 0 transport_latency_assumed tick_size_change c 2,464 not meas. 4ms 6ms 117ms 337ms 0 transport_latency_assumed tick_size_change e 2,464 2,464 42ms 102ms 231ms 524ms 0 transport_latency_assumed tick_size_change h 2,464 not meas. 18ms 20ms 50ms 558ms 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/19/2026-09-03T19.parquet sha256sum 2026-09-03T19.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.