Burns
How much supply is really gone, and from which wallet.
"We burned 30% of the supply."
CHECKERIs the devtelling thetruth?
Tag @Checker_fun under a dev's post. We check the chain and answer in the thread: yes, no, or not enough evidence.
Facts from public chain dataEvery verdict links its evidenceNever guesses
How it works
Tag. Check. Verdict.
No forms and no dashboards. One reply under the post is the whole product.
1
Tag Checker
Reply under the dev's post with @Checker_fun is this true? We read the post you replied to and answer in the thread.
2
We check the chain
An AI turns the post into a plain claim. Then fixed code, not the AI, finds the token and reads the real transactions.
3
Get the verdict
A short reply in the same thread with the evidence link. A full page shows every wallet and transaction.
What Checker verifies
Claims that the chain can answer.
Solana first. Each check reads real transactions and token accounts, then compares them with what the dev said.
Dev sells
Swaps from the deployer wallet and from wallets it sent tokens to.
"Dev hasn't sold."
Wallet moves
Tokens or SOL sent out, and whether the receiving wallets are new.
"We never moved these tokens."
Buybacks
Purchases of the token by the dev wallet, in SOL and dollars.
"Dev bought $10k today."
Supply
Top holders, dev share and total supply, with pools left out.
"Top 10 hold under 15%."
Funding
Where a wallet's first SOL came from, and whether wallets share a funder.
"These wallets are unrelated."
Authorities
Is the mint or freeze authority really revoked.
"Mint authority revoked."
Liquidity soon
Pool creation, LP burns and locks.
"LP is burned."
And much more
If the chain can answer it, Checker can read it. New kinds of claims are added as they become reliable, and anything it cannot check yet is answered "inconclusive", never guessed.
How it decides
Three answers. No scores.
Checker would rather say "inconclusive" than guess. There is no trust score and no vibes.
Yes
Verified
The chain data matches the claim, and Checker links the transactions that prove it.
No
False
A recorded fact contradicts the claim, for example a swap from the deployer wallet.
Maybe
Inconclusive
Not enough evidence: unclear token, wallets that cannot be tied to the team, or data that could not be read.
- The AI only reads the post. Fixed code decides the verdict from chain data. The AI never invents a result.
- A broken data source is never "false". If the chain data cannot be read, the answer is inconclusive.
- Wallets are described, not accused. "Linked by token transfer" is a fact; who owns a wallet is not claimed.
- Ambiguous token means no verdict. Two tokens with the same ticker? Checker asks for the contract address.
- Evidence stays attached. Every transaction link, timestamp and reason is saved on the check page.
- Facts, not accusations. Checker says what happened on-chain and nothing about intent.
Try it without X
Check a post here.
Paste a link to a post on X, or the text of the post. Same engine as the bot.
…free checks left todayNo sign-up. Resets every day.
Works best with the contract address in the post. 5 free checks a day per visitor, no sign-up.