Open data · CC0 · updated daily
A public channel calls pump.fun tokens. This is its complete record: 3,544 calls, each with the market cap it was called at, the highest multiple it reached afterwards, and the exact second it was posted. About six calls in ten never double — those are in the file too.
Most published track records are a screenshot of the winners. The point of this one is that it cannot be edited after the fact: the file is hashed, and the hash sits in a Bitcoin block.
The low entry cap is the whole point: calls are made on the bonding curve, before migration — not after a chart has already moved. The largest so far is CATE, called at $21,077 and peaked at 4,167×.
| field | meaning |
|---|---|
mint | Token mint address on Solana (base58) |
sym | Ticker as it appeared on pump.fun at call time |
t · utc | Publication time — unix seconds and ISO-8601 |
mc | Market cap in USD at the moment of the call — the entry reference |
peak | Highest multiple reached after the call. Ratchet: never revised down |
tg | Message number in the public channel, so any row can be traced back |
{"mc": 21077, "mint": "Ai66LHZG9MCzg1WKdawwqduVAXpNDUuV8M3uyq5ppump",
"peak": 4167.35, "sym": "CATE", "t": 1785083184, "tg": 4448,
"utc": "2026-07-26T16:26:24Z"}
Three commands. The first two prove the file has not been touched since it was stamped; the third lets you pick any row and look it up on-chain yourself.
# hash the file — must equal "sha256" in attest.json sha256sum calls.jsonl # confirm that hash is anchored in a Bitcoin block ots verify calls-a.ots # recompute every number claimed in the README, from the file python3 verify.py
Why the Bitcoin stamp matters. A trading record is only evidence if it cannot grow a winner in hindsight. Adding, editing or back-dating a single row changes the hash, and the old hash is already in a block — nobody can move it, including us.
peak says the token reached that multiple, not that
anyone sold there. Peak on a chart and money in a pocket are different things.The calls are published live on a Telegram channel; the file is rebuilt and re-stamped every night. Methodology, the live version of these numbers and the research built on the same feed are on the site:
verify.py and the OpenTimestamps receipts