Hour audit: 2026-08-28T18
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-28T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T18:00:00.015832574+00:00 · last event 2026-08-28T18:59:59.999989454+00:00
VOLUME 109,299,808 rows · 1,230,840,926 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 107,643,084 · e: 106,583,496 · h: 103,469,012 · a: 103,124,677 · b: 93,210,479 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · e: not measured · h: not measured · a: not measured · b: not measured (rows of the merged file that came from it; these partition it)
INTEGRITY sha256 73238124ac46df5759960f3518a632d821677e2a78506046f03a4f73646524e0
the corpus checksum ledger names this file with the same digest
joined 109,302,369 to merged 109,299,808, minus 2,561 (minus 0.0023%)
boundary drops 2,561 · 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 8,696,020 105,560,084 0-33 b41be1c336cdbaabcc77d53aa9ab3605461c3f852e4757d54c845b7150cceace book 1,811,870 96,164,705 34-40 b239b3239e5dade757680d597cf2a75a2aa4669629dedc1b3e8261155497f22d last_trade_price 82,273 4,725,368 41-41 0a0294b9f8dd846e9adc653aaad9d1479c3b9220068f98cfb3a9a0c19073abee market_resolved 1,142 163,594 42-42 a99287c8760e4ee3475a7594c57164a9a5d10045fd76920a8f9f88ddf14cb9d7 new_market 1,959 199,436 43-43 fd1f13e46d34514238030b8dda00867e8411495a6562c83e7c1555419c6a1a9d price_change 98,699,872 1,022,537,300 44-420 9b9e93d7de19c9bac26c107675e4a63688ea8cc0a863fc19f46bfee4edbde862 tick_size_change 6,672 243,960 421-421 de55fee976ccacda5c597b4957804497876e241d36c9ed42bc8661c45caf19c3 EVENT MIX count share price_change 98,699,872 90.30% best_bid_ask 8,696,020 7.96% book 1,811,870 1.66% last_trade_price 82,273 0.08% tick_size_change 6,672 <0.01% new_market 1,959 <0.01% market_resolved 1,142 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,696,068 8,696,020 48 2,603 FULL book 1,813,436 1,811,870 1,566 182,038 FULL last_trade_price 82,273 82,273 0 477 FULL market_resolved 1,142 1,142 0 104 FULL new_market 1,960 1,959 1 11 FULL price_change 98,700,818 98,699,872 946 1,269 FULL tick_size_change 6,672 6,672 0 409 FULL
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-28/18/2026-08-28T18.parquet sha256sum 2026-08-28T18.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.