Hour audit: 2026-08-28T08
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-28T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T08:00:00.019530636+00:00 · last event 2026-08-28T08:59:59.999972225+00:00
VOLUME 91,750,623 rows · 943,383,437 bytes (899.68 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 91,638,745 · a: 91,614,139 · b: 91,502,148 · h: 91,495,715 · e: 91,360,330 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · a: not measured · b: not measured · h: not measured · e: not measured (rows of the merged file that came from it; these partition it)
INTEGRITY sha256 53e915c5eacc8a9a017dc0f8e4727583e8365b101308090407ce7b13210d4fd5
the corpus checksum ledger names this file with the same digest
joined 91,751,765 to merged 91,750,623, minus 1,142 (minus 0.0012%)
boundary drops 1,142 · 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 an incident recorded by the venue intersects this hour: Venue maintenance on a market this archive does not record, 2026-08-28T08:00Z to 2026-08-28T08:40ZThe 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,633,879 102,109,140 0-32 21aa758e77167495bb08c1be663c915027430e767e6bdf8b5a5ae7865affa745 book 227,500 23,169,793 33-33 fe2a10590115aa0e80ade0f7a77531c9e8b9852835036db98deb0299eea12d57 last_trade_price 59,974 3,404,701 34-34 c3fcd6a9dc07db5e364ab72ea50ed459630081910cf422cce2b1cb0450e43612 market_resolved 498 81,897 35-35 6f78e863f1007e9f3121bd72c7bab8ded9618c76761794d147422e2be6adb240 new_market 650 69,528 36-36 82ea87930b7569c86fb47ebadd690a2ff9a3c2a97c4b2b9ede9f4e60b3f3fbfb price_change 82,825,354 813,399,801 37-352 11b05302528ca8473f44d2557e7de2199e900f55658944e3ed8a73ae82f02034 tick_size_change 2,768 102,774 353-353 398ae3aaf7d9812a89c054f576e2ab32d49683ea5840a530ce96e4295c54cf02 EVENT MIX count share price_change 82,825,354 90.27% best_bid_ask 8,633,879 9.41% book 227,500 0.25% last_trade_price 59,974 0.07% tick_size_change 2,768 <0.01% new_market 650 <0.01% market_resolved 498 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,633,981 8,633,879 102 124 FULL book 227,636 227,500 136 44,276 FULL last_trade_price 59,974 59,974 0 0 FULL market_resolved 498 498 0 0 FULL new_market 650 650 0 0 FULL price_change 82,826,258 82,825,354 904 175 FULL tick_size_change 2,768 2,768 0 0 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/08/2026-08-28T08.parquet sha256sum 2026-08-28T08.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.