Hour audit: 2026-08-29T13
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-29T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T13:00:00.036866933+00:00 · last event 2026-08-29T13:59:59.999942840+00:00
VOLUME 98,583,789 rows · 1,028,928,349 bytes (981.26 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 98,291,470 · a: 98,285,298 · h: 98,284,601 · e: 98,158,478 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · a: not measured · h: not measured · e: 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 3348dd876d08519c12df868713e028f5982502b5cb7fa31d0bb5958e67e3d8bb
the corpus checksum ledger names this file with the same digest
joined 98,585,453 to merged 98,583,789, minus 1,664 (minus 0.0017%)
boundary drops 1,664 · 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,730,038 101,603,630 0-33 6c41715904b11eafcc7ac94352c1e9e72d94005ada371d32179d16f2c0e6c725 book 524,912 48,191,685 34-36 3352fc563eef62a047c330a656660225fb38e62db8372f319f8949abe0e2d3a0 last_trade_price 68,629 3,932,413 37-37 cba255d084db314979dc4dc3d7dfea545b23800e59999ce0ad50d47d9948a48a market_resolved 1,242 187,250 38-38 20b1879afbda26b3ae2be9dd7df8c9d475a085a4a7ee8dbd73c54b023219a91b new_market 966 108,509 39-39 a8647ad470273f136ce59be6b9276d4dc2225fd15fe46b5eff08d1cb3e6db5d3 price_change 89,252,070 873,562,347 40-380 15def81457f5d3fc08def1ccbe42f88116392946314eff3c4e4a51dc28ee7542 tick_size_change 5,932 215,361 381-381 560a13d72207fd1d2ff28913c5c1691b6e3ae8351658c4e722e2ce06ef6fd2bf EVENT MIX count share price_change 89,252,070 90.53% best_bid_ask 8,730,038 8.86% book 524,912 0.53% last_trade_price 68,629 0.07% tick_size_change 5,932 <0.01% market_resolved 1,242 <0.01% new_market 966 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,730,150 8,730,038 112 93,286 PARTIAL book 525,396 524,912 484 136,480 PARTIAL last_trade_price 68,629 68,629 0 5,203 PARTIAL market_resolved 1,242 1,242 0 1,169 PARTIAL new_market 966 966 0 705 PARTIAL price_change 89,253,138 89,252,070 1,068 143,839 PARTIAL tick_size_change 5,932 5,932 0 1,483 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,727,678 not meas. 38ms 46ms 257ms 11.5s 0 not stated best_bid_ask c 8,729,200 not meas. 4ms 8ms 69ms 8.2s 0 not stated best_bid_ask e 8,722,139 not meas. 44ms 88ms 667ms 27.5s 0 not stated best_bid_ask h 8,728,658 not meas. 12ms 18ms 109ms 7.6s 0 not stated book a 256,935 not meas. 758ms 1.7h 21.0d 91.7d 0 not stated book c 245,779 not meas. 15ms 1.2h 21.0d 91.7d 0 not stated book e 245,562 not meas. 1.2s 1.3h 21.0d 91.6d 0 not stated book h 242,095 not meas. 44ms 1.3h 21.0d 91.6d 0 not stated last_trade_price a 68,515 not meas. 48ms 757ms 6.9s 11.5s 0 not stated last_trade_price c 68,604 not meas. 9ms 39ms 210ms 5.0s 0 not stated last_trade_price e 67,417 not meas. 61ms 2.0s 10.2s 27.5s 0 not stated last_trade_price h 68,544 not meas. 18ms 70ms 592ms 7.0s 0 not stated market_resolved a 1,169 not meas. 39ms 316ms 54.4s 1.9min 0 not stated market_resolved c 1,169 not meas. 4ms 14ms 56.1s 57.5s 0 not stated market_resolved e 1,169 not meas. 44ms 375ms 54.4s 60.0s 0 not stated market_resolved h 1,169 not meas. 13ms 47ms 130ms 3.6s 0 not stated new_market a 705 not meas. 236ms 15.3s 27.0s 1.0min 0 not stated new_market c 705 not meas. 69ms 15.7s 23.2s 1.1min 0 not stated new_market e 705 not meas. 209ms 16.1s 25.4s 1.3min 0 not stated new_market h 705 not meas. 117ms 11.7s 23.8s 52.0s 0 not stated price_change a 89,224,364 not meas. 38ms 56ms 504ms 11.6s 0 not stated price_change c 89,240,081 not meas. 4ms 8ms 99ms 9.0s 0 not stated price_change e 89,115,554 not meas. 45ms 127ms 2.4s 27.6s 0 not stated price_change h 89,237,498 not meas. 12ms 19ms 154ms 8.3s 0 not stated tick_size_change a 5,932 not meas. 38ms 42ms 130ms 778ms 0 not stated tick_size_change c 5,932 not meas. 4ms 7ms 21ms 269ms 0 not stated tick_size_change e 5,932 not meas. 45ms 110ms 249ms 9.4s 0 not stated tick_size_change h 5,932 not meas. 12ms 16ms 38ms 184ms 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/13/2026-08-29T13.parquet sha256sum 2026-08-29T13.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.