Index of /pmxt/v1/
Format, provenance and known issues for this data: V1 · mirror. What we measured about it, and where it falls short: the audit.
Historical data 2026-02-21T18 → 2026-04-16T05 collected and published by PMXT at archive.pmxt.dev, CC BY 4.0. Mirrored unmodified.
1 hour
in this era is absent from what PMXT
published: 2026-04-04T18. We mirror this
prefix unmodified and did not remove it. The audit carries
the count and how it was taken.
What is wrong with this data
Treat v1 as a partial sample of its era: useful for presence and shape, never for completeness claims.
- About a third of traded markets are missing. Against on-chain fills, v1 has a book for 65.00% of the markets that traded, across the six hours we picked in advance for the audit, ranging 32.24% to 99.94% hour by hour. Separately, on the hours v1 shares with v2, v1 lacks 41.93% of the markets v2 holds, and v2 lacks 2.28% of the markets v1 holds. Two methods with no shared input point the same way. the audit's check against on-chain fills, and the v1 to v2 overlap comparison, 2026-08-31
- Roughly half of v1's fills are phantom, and that is the venue's behaviour rather than a fault in this archive. 46% to 48% in every measured v1 hour. Polymarket's relayer reported fills that the on-chain contracts then rejected; traders called these ghost fills, and Polymarket's own exchange upgrade of 2026-04-28, which brought new contracts, a rewritten order book, and fees charged at match time instead of order time, was aimed squarely at that class of failure. PMXT recorded what the venue reported, which is what an archive is supposed to do. The phenomenon ends at 2026-06-19: markets from that date onward carry none. No market is entirely phantom: every traded market has at least one real fill. So this affects fill counts, not which markets appear. Polymarket's note on the upgrade. the audit's check against on-chain fills for the percentages, Polymarket's upgrade notes for the cause, 2026-08-31
- The real data ends earlier than the listing suggests. v1's last hour with data is 2026-04-15T08. The 21 hours listed after it, 2026-04-15T09 to 2026-04-16T05, are zero-row placeholder objects of 214 bytes each. They are listed because the files exist. They hold nothing. hour census against the published v1 SHA256SUMS.txt, with object sizes, 2026-08-31
- No transaction hashes, so individual fills cannot be matched to the chain. v1 records no trades and has no transaction_hash column, so individual fills cannot be matched to the chain. The coverage ratio above matches markets, not fills. read from the files, 2026-08-28
1,224 of v1's 1,283 hours have no v2 hour beside them, so nothing there can show what v1 missed.
Checksums for this prefix:
SHA256SUMS.txt, verify a download with
sha256sum -c.
Download this prefix in bulk
You do not need to open the hour pages, and you should not scrape this one.
SHA256SUMS.txt lists every file under this prefix, so it is both the
download list and the verification file.
# every file URL under /pmxt/v1/
curl -s https://archive.pendulumflow.com/pmxt/v1/SHA256SUMS.txt | awk '{print $2}' \
| sed 's|^|https://archive.pendulumflow.com/pmxt/v1/|'
# fetch them, four at a time, keeping the directory layout
curl -s https://archive.pendulumflow.com/pmxt/v1/SHA256SUMS.txt | awk '{print $2}' \
| xargs -P4 -I{} curl -sf --create-dirs -o {} https://archive.pendulumflow.com/pmxt/v1/{}
# then verify the lot, in the directory you downloaded into
curl -sO https://archive.pendulumflow.com/pmxt/v1/SHA256SUMS.txt && sha256sum -c SHA256SUMS.txt
# fetched only PART of it? filter the ledger to MATCH WHAT YOU TOOK
grep <the prefix you fetched> SHA256SUMS.txt | sha256sum -c -Fetched only part of it? Filter the checksum list to what you took first, for example
grep 2026-04-16 SHA256SUMS.txt | sha256sum -c - for one day, or every file you
skipped prints as FAILED.
Add | grep 'parquet$' to skip the manifests. Ranges within a file work
too, see the format notes.
1283 objects.
Looking for data we don't publish yet? Tell us.
Pendulum Flow Discord
Something wrong with an hour, or a file you need that is not here? Say so in the Discord, where the people who run the site and prediction market data geeks compare notes.
Join the Discord