Hour audit: 2026-08-29T14
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-29T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T14:00:00.034536953+00:00 · last event 2026-08-29T14:59:59.999977465+00:00
VOLUME 112,029,066 rows · 1,199,786,869 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 111,560,772 · c: 111,559,169 · e: 110,963,260 · a: 107,333,648 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · c: not measured · e: not measured · a: not measured (rows of the merged file that came from it; these partition it)
28 product-machine pairs publish no supplied count, and the figures above do not reconcile to the file's row count, so the split is incomplete by an unrecorded amount
INTEGRITY sha256 bd44ad45dcc3c7e8f1127b73dbed877d7320f1f6c84436ab4212f0341f18cbb7
the corpus checksum ledger names this file with the same digest
joined 112,031,389 to merged 112,029,066, minus 2,323 (minus 0.0021%)
boundary drops 2,323 · 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 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 7/8 pass, 1 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
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 10,422,914 120,023,892 0-39 3f9ffbc649fd2314926b24f08649414bfff58033786a65f5ab156b35c9f04024 book 673,313 60,040,160 40-42 30d811c808352f0a3d672664121d1c01589b30776594868dea66bbb0a2b6466f last_trade_price 72,652 4,223,875 43-43 b1f349e69297263b5176845505d33e97a64544ef43c236f97158043d0678b3f0 market_resolved 1,912 298,929 44-44 e6befe7d81b84e18b8460e94ef4adb73e5b150bd4320c62560fc488952a9a998 new_market 1,615 160,287 45-45 3642c9f9b99e305eeb5b461b9d4bf2e2f3c0466a5df3d78ce4840102399b2ecf price_change 100,848,656 1,013,479,398 46-430 8026021b2ac92fa6e2dd9bd9cfb591d6cd5601babef7b53eaa251e2b7fa544a7 tick_size_change 8,004 286,306 431-431 f2a65049cc6a6fbd3c5fce283e3076581715b8c9956a93c61a3b1767e820b231 EVENT MIX count share price_change 100,848,656 90.02% best_bid_ask 10,422,914 9.30% book 673,313 0.60% last_trade_price 72,652 0.06% tick_size_change 8,004 <0.01% market_resolved 1,912 <0.01% new_market 1,615 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,423,094 10,422,914 180 87,003 PARTIAL book 673,887 673,313 574 183,103 PARTIAL last_trade_price 72,653 72,652 1 5,164 PARTIAL market_resolved 1,912 1,912 0 1,853 PARTIAL new_market 1,615 1,615 0 1,040 PARTIAL price_change 100,850,224 100,848,656 1,568 145,096 PARTIAL tick_size_change 8,004 8,004 0 2,001 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 10,012,855 not meas. 39ms 50ms 309ms 11.2s 0 not stated best_bid_ask c 10,421,980 not meas. 4ms 9ms 103ms 3.4s 0 not stated best_bid_ask e 10,402,193 not meas. 45ms 120ms 1.6s 38.9s 0 not stated best_bid_ask h 10,421,247 not meas. 12ms 23ms 134ms 9.6s 0 not stated book a 535,434 not meas. 54.4s 6.2h 25.7d 91.7d 0 not stated book c 213,373 not meas. 10ms 6.7min 21.0d 91.7d 0 not stated book e 218,127 not meas. 859ms 11.8min 21.0d 91.7d 0 not stated book h 219,022 not meas. 31ms 8.0min 21.0d 91.7d 0 not stated last_trade_price a 69,268 not meas. 55ms 2.1s 8.3s 11.3s 0 not stated last_trade_price c 72,623 not meas. 9ms 39ms 217ms 5.0s 0 not stated last_trade_price e 69,683 not meas. 79ms 4.7s 14.5s 39.0s 0 not stated last_trade_price h 72,580 not meas. 18ms 87ms 631ms 8.1s 0 not stated market_resolved a 1,747 not meas. 40ms 169ms 55.1s 59.5s 0 not stated market_resolved c 1,853 not meas. 4ms 11ms 57.5s 1.0min 0 not stated market_resolved e 1,853 not meas. 45ms 206ms 56.6s 1.0min 0 not stated market_resolved h 1,853 not meas. 12ms 46ms 207ms 1.0s 0 not stated new_market a 969 not meas. 220ms 25.4s 3.8min 3.8min 0 not stated new_market c 1,040 not meas. 77ms 19.5s 57.7s 1.2min 0 not stated new_market e 1,040 not meas. 204ms 18.6s 53.4s 1.2min 0 not stated new_market h 1,040 not meas. 126ms 20.6s 59.5s 1.5min 0 not stated price_change a 96,705,815 not meas. 39ms 70ms 1.0s 11.3s 0 not stated price_change c 100,840,296 not meas. 4ms 9ms 139ms 5.1s 0 not stated price_change e 100,262,360 not meas. 46ms 222ms 6.3s 39.1s 0 not stated price_change h 100,837,026 not meas. 12ms 26ms 193ms 9.9s 0 not stated tick_size_change a 7,560 not meas. 39ms 44ms 239ms 968ms 0 not stated tick_size_change c 8,004 not meas. 4ms 8ms 167ms 676ms 0 not stated tick_size_change e 8,004 not meas. 45ms 118ms 1.4s 9.0s 0 not stated tick_size_change h 8,004 not meas. 12ms 20ms 134ms 563ms 0 not stated
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-08-29/14/2026-08-29T14.parquet sha256sum 2026-08-29T14.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.