About BurnBook

How an entry gets published

1. Someone submits a report with identifiers (wallet, handle, domain) and evidence.
2. The submission sits in a private moderation queue. It is not public yet.
3. A moderator reviews the evidence. They can approve it (publishing a new or updated profile), reject it, or request more information from the submitter.
4. Only once approved does a profile (and the evidence behind it) become publicly visible.

This means nothing is published purely on accusation. That said, BurnBook is a community reporting tool, not a court: moderators verify that evidence was submitted and is plausible, not that every claim is conclusively proven.

What we prioritize

Hundreds of scam tokens launch every day. BurnBook doesn't try to catalog all of them, that's not a realistic goal for a community-moderated project, and most one-off anonymous coins have little lasting search value anyway. Review is prioritized toward named individuals over anonymous one-off projects (a person can launch the same scam again under a new name; a dead coin usually can't), reports on entities already documented here, and submissions backed by verifiable evidence like transaction hashes or screenshots rather than a bare claim. If your report doesn't get reviewed right away, this is why, and it doesn't mean it was dismissed.

Other resources

BurnBook focuses on documented, evidence-backed cases and the people behind them. It isn't a real-time contract scanner or an exhaustive address blocklist, and for those, other tools do a better job:

Before you buy a token: RugCheck (Solana), TokenSniffer, and Honeypot.is scan the contract itself, checking things like locked liquidity, ownership renouncement, and whether a token can actually be resold, before you ever put money in.

Broader scam-address lookups: Chainabuse and CryptoScamDB maintain large, actively updated databases of reported scam wallets and phishing domains across chains.

We don't vouch for the accuracy of any of these any more than we can vouch for our own, cross-check what you find, here and elsewhere.

Identity & doxxing policy

Profiles are anchored to on-chain and public identifiers (wallet addresses, ENS names, X/Telegram/Discord handles, domains, and project names) rather than private personal information. We do not knowingly publish home addresses, phone numbers, national ID numbers, or other private contact information, even if a submitter provides them. Open the entry in question and use the "Report a problem" link at the bottom of the page and we will remove it.

A real name may appear on a profile only where the individual has already publicly and voluntarily tied that name to the project or activity in question (e.g. a doxxed founder), and only alongside supporting evidence.

Right of reply

Anyone listed on BurnBook can respond. Open the profile in question and click "File a dispute" to submit a statement, with supporting links if you have them. Disputes go through the same moderation queue and, once published, appear directly on the profile alongside the original evidence. We don't take listings down on request alone, but we do publish the other side.

Legal disclaimer

Content on BurnBook is user-submitted and reflects allegations, not adjudicated legal findings. "Documented" means a moderator confirmed evidence was submitted and found it credible enough to publish, not a determination of guilt, fraud, or criminal liability. Use independent judgment and your own due diligence before making financial decisions based on anything here.

If you believe an entry is false, defamatory, or violates this policy, use that entry's "Report a problem" link, or file a dispute if you're the subject and want to respond publicly. This page is provided for transparency and is not legal advice.

Report categories

Rug pull, exit scam, honeypot (can't sell), phishing, impersonation, fake/doxx-faked team, Ponzi or unsustainable yield, pump and dump, wash trading, theft of funds, and fake audits/KYC. Submitters can also select "other" for anything that doesn't fit cleanly.

About the creator

BurnBook is built and run by @magikarpmilk. I'm new to crypto, and one of the first things I noticed since poking my head through the door is how often someone gets called a "scammer" or "rugger" in a reply thread, with no way to check if that's true, or find out what actually happened, once the tweet scrolls by. The tools that already exist are mostly built for scanning contracts or logging flagged wallet addresses, not for reading the actual story, seeing the evidence, or hearing the accused's side. There wasn't a beginner-friendly place to look any of it up, or to share insights and experiences with bad actor "devs": the kind of thing that could actually help prevent someone else's future loss. BurnBook is an attempt at building that.

If you find this useful and want to help cover hosting and moderation costs, donations are welcome (SOL):