How a promise is checked
A model may help read the text. It never decides. Every mark below is computed by code from the chain, and every number links to the transaction or account it came from.
0How it works, on film
One case file, read the way the desk reads it: the sources, the marked promises, the date, the thread to the chain, the stamps. Voiced, with captions burned in.
1What the agent reads
Only the coin's own sources: the pump.fun metadata (description, links), posts on X it links to, the project site, the profile bio. A base check reads one page of the site and up to five posts; a deep check three pages and up to thirty posts. Quoted and replied-to posts are followed one hop.
Sites are fetched as plain pages, robots.txt is respected, and a headless browser is used only when a page has almost no text. Every failure is filed in the report's source list with the reason.
2How we read X
There is no free way to read an account's timeline or its pinned post in 2026. We read posts by their links: the link in the coin's metadata, links on the site and in the bio, and any link you paste. Each post is fetched from public post endpoints (one request a second for the whole desk, posts cached for good, profiles for six hours).
If a post cannot be read, the report says so and the paste box stays open: paste the post link, or the text itself. Pasted text is labelled as the reader's, is checked from the coin's launch, and never counts in the tally or the share card.
3The window
A promise is checked only after it was said. The window is W = [said, now].
- Post on X - the post's own time, read from its id.
- pump.fun metadata - the coin's create transaction.
- Site or bio - the first time we saw that sentence (we keep a snapshot of every sentence).
- Pasted - the coin's launch, labelled.
The same promise found in two sources keeps the earliest one, so a repeat does not restart the clock.
4The marks
- Kept
- The chain shows it. For promises with a rhythm, at least 80% of the judged periods.
- Partly
- Some of it: 20-80% of the periods, part of the amount, or done but not the way it was said (bought back, not burned).
- No record
- We looked where it must show and found no matching transaction after it was said. Not an accusation: a buyback from a wallet nobody named is invisible to anyone.
- Too early
- The promise has a date ahead, or the coin is still on the curve for an LP promise, or there is no fee income yet.
- Can't verify
- Nothing on the chain can show it either way.
Periodic promises ("daily buyback", "weekly burn"): P = floor(W / period), the first period is grace, judged = P - 1. Kept when covered / judged >= 0.8, partly from 0.2, otherwise no record.
5Each kind of promise
- Burn
- Burned = minted in the create transaction - supply now + tokens at the incinerator. Split by who burned: project wallets, pump's own buy-and-burn, other holders, unattributed. Only project burns count. A base check scans the 3 newest pages of the mint; deep, 30; a cut scan says "within the scanned range".
- LP lock
- Not a pump coin: can't verify. On the curve: too early. LP supply at zero after migration: kept, with the migration transaction. LP held by lock programs: kept at 95% or more, else partly with the share.
- Token lock
- Top 20 holders resolved to lock programs (Jupiter Lock decoded; Streamflow, Bonfida, Raydium lock shown as locked). Locked vs promised: 95% kept, 20-95% partly, none: no record. Cancelled or fully unlocked: no record since that date.
- Buyback, buyback & burn
- Buys of the coin by project wallets in the window, net of sells (buy-then-sell is not a buyback), against the fees claimed in the window plus unclaimed fees. "And burn": at least 90% of the bought amount burned within 24 h, else partly.
- Holder payouts
- Runs of sends (within 10 minutes) from project wallets to 10 or more recipients, half of them current holders. Pump fee-sharing distributions are counted separately. "x% reflection per transaction" on a token without a transfer fee: no record.
- Fee sharing
- The pump fee-sharing config: present, routed, admin revoked and the promised share present: kept; otherwise partly with the reason. Who owns a receiving wallet in real life is never claimed.
- Dev bag
- Dev = the signer of the create transaction. Held at the promise vs sells and transfers after it: none, kept; a transfer only, partly ("moved, not sold"); sold up to 20%, partly; more, no record. Already sold before the promise: no record.
Project wallets: the creator, the fee admin and shareholders, wallets named in the coin's own sources. Wallets a reader adds give a separate, labelled view and never change the mark.
6What can't be verified
Marketing and trending, exchange listings, partnerships, roadmaps and feature dates, and who owns a wallet in real life. The report quotes them and marks them can't verify instead of guessing.
7Known limits
- Holders for payouts are today's holders, not a snapshot at payout time.
- Streamflow schedules are not decoded: shown as locked, partly at best.
- The phrase list misses wording it does not know. Every promise has "Not a promise" and "Wrong mark" buttons, and popular reports are re-checked every hour.
- A site sentence dates from when we first saw it; there is no web archive lookup yet.
8Free and deep
A base check is free, with a daily limit per address. A report already on file is free to open. A deep check costs a small SOL payment verified by its transaction, or is free for holders of the pad's token, signed with the wallet. Nothing is ever asked of the coin's dev. Not financial advice.