Hour audit: 2026-08-29T11
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-29T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T11:00:00.033484180+00:00 · last event 2026-08-29T11:59:59.999999934+00:00
VOLUME 101,589,172 rows · 1,080,012,556 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 101,205,652 · h: 101,204,086 · e: 101,177,863 · a: 97,283,002 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: 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 49d778189c663e1673f4b7c1d4cf406210e8cdd2ff5f580bca3452fce34a8afb
the corpus checksum ledger names this file with the same digest
joined 101,590,172 to merged 101,589,172, minus 1,000 (minus 0.0010%)
boundary drops 1,000 · 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 7,338,784 86,591,827 0-27 1df453f9183ccbb91ecfb0214b810090d20b6781b2a79d2ff4075b203f7db311 book 507,666 53,716,340 28-29 10ef548314b9f0ada02add994d0bb139ace56ea298196b13782fa61a95def854 last_trade_price 63,727 3,722,077 30-30 c4c3530c22f50243b8667855ab1481c8957241974f8ddbb70a97d6f74154b51a market_resolved 776 119,000 31-31 d4f1b69d170a8919d1141851b7ce4d43b0824314fdca82c9bf3bf08d9b18a092 new_market 655 73,663 32-32 eb0e8e77bb5605fad3e77c19c04411feb2f5fb71ba6fda1a4c92289dd818b997 price_change 93,671,048 934,394,997 33-390 1bc0cc5967b62897a2cd4001f3f2a739c96c83222e80648a3e98c54ac4059ca1 tick_size_change 6,516 237,404 391-391 2b29e9ecd3f00b5e20414a5712fc8e9a8689daf666ef6f9bbb118c70bbdc2f4f EVENT MIX count share price_change 93,671,048 92.21% best_bid_ask 7,338,784 7.22% book 507,666 0.50% last_trade_price 63,727 0.06% tick_size_change 6,516 <0.01% market_resolved 776 <0.01% new_market 655 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,338,879 7,338,784 95 71,019 PARTIAL book 507,678 507,666 12 184,068 PARTIAL last_trade_price 63,728 63,727 1 4,820 PARTIAL market_resolved 776 776 0 730 PARTIAL new_market 655 655 0 480 PARTIAL price_change 93,671,940 93,671,048 892 136,819 PARTIAL tick_size_change 6,516 6,516 0 1,629 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,024,769 not meas. 39ms 46ms 228ms 13.5s 0 not stated best_bid_ask c 7,338,446 not meas. 4ms 7ms 62ms 10.8s 0 not stated best_bid_ask e 7,336,319 not meas. 44ms 95ms 1.1s 17.4s 0 not stated best_bid_ask h 7,337,944 not meas. 12ms 17ms 90ms 6.7s 0 not stated book a 494,221 not meas. 56.5s 5.0h 25.6d 91.5d 0 not stated book c 132,011 not meas. 7ms 20ms 8.8s 73.1d 0 not stated book e 136,889 not meas. 52ms 3.4s 4.1h 45.8d 0 not stated book h 130,895 not meas. 17ms 56ms 869ms 73.0d 0 not stated last_trade_price a 60,092 not meas. 48ms 443ms 5.5s 9.6s 0 not stated last_trade_price c 63,705 not meas. 9ms 38ms 195ms 6.3s 0 not stated last_trade_price e 63,347 not meas. 59ms 1.4s 9.0s 17.4s 0 not stated last_trade_price h 63,653 not meas. 17ms 64ms 614ms 5.8s 0 not stated market_resolved a 677 not meas. 40ms 378ms 5.0min 5.0min 0 not stated market_resolved c 730 not meas. 4ms 9ms 171ms 664ms 0 not stated market_resolved e 730 not meas. 45ms 215ms 1.6s 2.5s 0 not stated market_resolved h 730 not meas. 12ms 64ms 275ms 890ms 0 not stated new_market a 481 not meas. 172ms 675ms 23.1s 4.4min 0 not stated new_market c 480 not meas. 55ms 12.2s 24.6s 25.9s 0 not stated new_market e 480 not meas. 177ms 12.4s 16.8s 18.5s 0 not stated new_market h 480 not meas. 86ms 13.7s 24.5s 1.0min 0 not stated price_change a 89,696,630 not meas. 39ms 55ms 455ms 18.7s 0 not stated price_change c 93,663,764 not meas. 4ms 8ms 115ms 11.6s 0 not stated price_change e 93,633,582 not meas. 44ms 123ms 2.4s 17.5s 0 not stated price_change h 93,663,868 not meas. 12ms 18ms 159ms 6.7s 0 not stated tick_size_change a 6,132 not meas. 39ms 43ms 137ms 804ms 0 not stated tick_size_change c 6,516 not meas. 4ms 7ms 21ms 364ms 0 not stated tick_size_change e 6,516 not meas. 44ms 100ms 240ms 4.2s 0 not stated tick_size_change h 6,516 not meas. 12ms 16ms 38ms 260ms 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/11/2026-08-29T11.parquet sha256sum 2026-08-29T11.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.