Bragsift Pons · CA at launch

● Docs

How Bragsift reads a coin

What it checks, how each line gets its status, and where it stops.

What it is

Bragsift puts what a Pons coin says next to what Pons and Robinhood Chain record for that coin. It reads the coin's Pons description, its website and its links, finds sentences that can be checked, and quotes them word for word. For each sentence it shows what Pons and Robinhood Chain record for that coin, with the link to the record.

It is not a score, a rating or advice. It has no wallet connection, no login and no smart contract; it only reads.

How to use it

  • Paste a Pons coin's contract address on the front page. No wallet, no login. The report page fills in while it runs and shows its place in the queue.
  • Share: every report has its own link, https://bragsfit.pro/c/<ca>, and a preview image with its counts.
  • Re-check: reports are cached for 10 minutes. Re-check runs a fresh report (once a report is 2 minutes old; the button shows the wait as text).
  • JSON: the same data as JSON at GET https://bragsfit.pro/api/check/<ca> — see API.

The four statuses

Every line is Matches, Doesn't match, Can't check, or No claim. There is no score and no verdict.

StatusMeaning
MatchesA quoted sentence agrees with the record.
Doesn't matchA quoted sentence differs from the record. Two lines use neutral variants: “Not shown” (CA on the website) and “Doesn't respond” (the website link).
Can't checkThe sentence cannot be compared with Pons or the chain, or the record could not be read (chain reads paused, site unreachable, budget used up). A reason is always shown, and a missing record is never shown as 0.
No claimNo checkable sentence was found for this line. The fact is still shown. Not counted.

Counts read “N checked · M match · K don't · J can't”, where checked = Matches + Doesn't match + Can't check.

How each line is checked

01 · Creator tax

Quotes any tax percentage the coin states and compares it with the creator tax Pons records for the coin.

Looks for sentences like “2% tax”, “0% tax”, “no tax” or “tax-free” (“no”, “zero” and “tax-free” count as 0 %). Matches when any stated percentage equals the creator tax Pons records (within 0.05 %); Doesn't match when none does.

02 · Bundle / whitelisted wallets

Quotes "no bundle / fair launch" style wording and compares it with the number of whitelisted wallets Pons lists.

Looks for “fair launch”, “no bundle”, “anti-snipe”, “no presale”, “no whitelist” and similar. Pons lists how many whitelisted wallets bought in the launch bundle. Matches when that number is 0; Doesn't match when it is above 0.

03 · Fee recipient

Quotes where the coin says fees go and compares it with the fee recipient and payout count Pons records.

Looks for “fees go to …”, “tax is distributed to …”. When the sentence names holders or the community: Matches when Pons routes creator fees somewhere other than the single creator wallet, or has recorded payouts; Doesn't match when fees go to the creator wallet with 0 payouts. Any other target (team, treasury, a wallet, a buyback) is Can't check: who owns a wallet is not something Pons or the chain records.

04 · Deployer wallet

Replays the token's Transfer events to show what the deployer wallet bought, sold, moved to other wallets and still holds, and compares it with any dev statement.

Replays every Transfer event since launch. Bought = tokens the market (the Pons curve, plus the Uniswap v4 PoolManager after graduation) sent to the deployer wallet, including the launch transaction; sold = tokens it sent to the market; moved = tokens it sent to other wallets (count of receivers + amount); holds = what is left. Statements like “dev won't sell”, “no dev tokens” or “dev holds” are compared with those numbers. Without such a statement the line is No claim and the numbers are still shown.

05 · Buyback / burn / lock

Quotes buyback, burn or lock wording and compares it with Pons's buyback setting, its payouts and the tokens sent to the burn address.

Buyback wording is compared with Pons's buyback setting and its payout count. Burn wording is compared with the tokens sent to the burn addresses 0x…dEaD and 0x0 (the mint is not counted). LP-lock wording is Can't check: LP locks are not visible on Pons v2 curves.

06 · Largest holders

Rebuilds balances from Transfer events and lists the ten largest wallets outside the market, with their share of supply.

Rebuilds every balance from the Transfer events, leaves out the market and the burn addresses, and lists the ten largest wallets with their share of supply and the holder count. This line has no quote; it is Can't check only when the events could not be read in full.

07 · Contract address on the website

Fetches the website Pons lists and looks for this contract address in its HTML.

Fetches the website Pons lists and searches its HTML for 0x + 40 hex characters. Matches when this contract address appears; Not shown when it does not (counted with Doesn't match); Can't check when the site could not be read.

08 · Links listed on Pons

Checks that the listed website responds and whether the X account it links is the one Pons lists. X itself is never fetched.

The website Matches when it answers with an HTML page; Doesn't respond on an error status, a DNS failure or a timeout; Can't check when it only renders in the browser or sits behind a browser challenge. For X, the handle Pons lists is compared with the X links in the site's HTML. Telegram, Discord and Farcaster links are shown, not checked.

09 · Stage

Quotes wording about graduating or listing and compares it with the stage Pons records.

Wording like “graduated”, “on Uniswap” or “listed on DEX” is compared with the stage Pons records (curve or graduated). “Listed on” an exchange is Can't check.

10 · Other statements

Quotes statements about audits, renounced ownership, KYC, partnerships or listings. These cannot be verified from Pons or the chain and are marked Can't check, with the reason.

Audits, “renounced”, KYC, “doxxed”, partnerships, “backed by”, exchange listings, guarantees and “100x”-style figures are quoted and always marked Can't check, each with its reason — for example “no audit record exists on Pons or the chain”.

How sentences are found

The Pons description and the website's visible text are split into sentences. Each sentence is tested against a short list of patterns per line (for example 2% tax, fair launch, buyback, dev won't sell, audited). A hit is quoted exactly as written, cut to at most 200 characters around the match (“…” marks the cut), with its source: Pons or Site. At most three quotes per line per source, 24 per report.

Sentences are found by pattern, not understood; a quote may describe the project's product rather than this coin — the quote and the source are always shown so you can judge.

No language model is involved: the same page and the same records give the same report.

Limits

  • Pons coins only. An address Pons does not know is answered with “This address is not a Pons coin.”
  • 12-day windows. The chain allows one query to span at most 10,000,000 blocks (about 12 days) and to return at most 10,000 events. Older coins: history is read in 12-day windows; coins with more transfers than the window budget show Can't check on the holders line.
  • 8-call budget. A report makes at most 8 full reads of the token's events. When a busy coin needs more, the holders and burn figures show Can't check with the reason and a link to the Blockscout holders list, and the deployer line is read with queries for that wallet's own transfers instead (the last 72 days plus the launch window for the oldest coins).
  • One shared lane. One shared lane to Robinhood's RPC: checks run one request at a time; a busy page shows its place in the queue. When the RPC asks to slow down, the lane pauses for 61 s and the page says so.
  • 10-minute cache. Reports are cached for 10 minutes. Re-check runs a fresh report, limited to once per coin every 2 minutes.
  • X is never fetched. X blocks servers, so posts are not read and whether an X account exists is not checked; only the handle text is compared.
  • Websites. The server fetches the listed site without running its scripts (public addresses only, at most 3 redirects, 12 s, the first 1 MiB). Sites that render only in the browser, or sit behind a browser challenge, show Can't check.
  • No price data of its own. Market cap, volume and trade count are shown as Pons reports them.

Not audited

Bragsift has no smart contract. The code has not been audited by a third party.

Data sources

  • Pons API — https://ponsfamily.com/api/launches/<ca>: description, deployer, creator tax, whitelisted wallets, fee recipient and payouts, buyback setting, stage, socials. Human link: https://ponsfamily.com/profile/<ca>.
  • Robinhood Chain RPC (mainnet, chain id 4663): the token's Transfer events, read from the server.
  • Blockscout — robinhoodchain.blockscout.com: every address and transaction link in a report opens here.
  • The coin's own website, as listed on Pons, fetched by the server.

Wording

Reports use neutral verbs — says, lists, shows, records, doesn't respond, not shown — and every fact names its source. Bragsift does not label coins or people: words such as scam, rug, fraud or honeypot are not used anywhere. A line is a comparison of a quoted sentence with a record, written in the third person (“the deployer wallet sold 8.57 M”), never a judgement of intent. All times are UTC.

API

Same data as JSON: GET https://bragsfit.pro/api/check/<ca>. CORS is open. Add ?fresh=1 to request a re-check.

200 { ca, status: "done", checkedAt, headBlock,
      coin: { name, symbol, deployer, createdAt, stage, tradeCount,
              volumeQuote, marketCapUsd, links: { pons, blockscout, website, twitter } },
      counts: { checked, match, mismatch, unverifiable, none },
      lines: [ { id, title, status, label, claims: [ { source, text } ],
                 fact: { text, data }, reason?, evidence: [ { label, url } ] } ],
      meta: { logsComplete, fullLogCalls, nWin, rpcOk, site } }
202 { status: "queued", queue: { position, etaSec, pausedSec } }   poll every 2 s
400 invalid_ca · 404 not_pons · 429 { retryAfterSec } · 503 pons_unavailable

Line ids, in order: tax, bundle, fees, deployer, buybackBurn, holders, caOnSite, links, stage, other. Status values: match, mismatch, unverifiable, none (and pending while a line is being computed).

Also: GET https://bragsfit.pro/api/board (the board) and GET https://bragsfit.pro/api/health (lane and data-source status). A plain-text summary for language tools is at /llms.txt.