A crypto whitepaper is supposed to be a technical and economic document describing a project's problem statement, solution, tokenomics, roadmap, and team in specific, verifiable detail. In practice, a significant proportion of presale whitepapers are copied from existing projects, generated by AI with minimal customisation, or deliberately vague to obscure the absence of a real product. Detecting these before investing takes specific techniques — and considerably less time than recovering losses from a scam.
10 Methods to Detect a Fake or Plagiarised Whitepaper
Method 1: Plagiarism Checker
Copy sections from the project description and technical solution chapters into Copyscape (copyscape.com), PlagScan, or Google search in quotes. Search for distinctive phrases. A legitimate whitepaper will have minimal exact matches to existing documents. A plagiarised whitepaper will return results from Ethereum, Solana, or other projects' documentation with near-identical text. Pay particular attention to the "problem statement" and "technology overview" sections — these are most commonly copied.
Method 2: AI Content Detection
Paste whitepaper sections into GPTZero (gptzero.me) or Originality.ai. These tools detect AI-generated text with reasonable accuracy. Fully AI-generated whitepapers (with no human customisation) indicate either very early-stage projects (understandable if disclosed) or deliberate misrepresentation (concerning). The key red flag is AI-generated content that makes specific technical claims that no human actually understands — the AI writes fluently but the team cannot explain the content.
Method 3: The "Talk to the Team" Test
Ask the team a specific technical question from their whitepaper in a public AMA or Telegram. If the whitepaper claims "we use zero-knowledge proofs for transaction privacy," ask: "Which ZK proof system do you use — Groth16, PLONK, or something else? What is the proving time and verification time?" Genuine technical teams answer specifically. Teams that copied technical content from another project cannot answer beyond what the whitepaper says — their answers will be vague or redirect to "our technical paper covers this."
Method 4: Date and Event Cross-Reference
Check the whitepaper's claims against historical facts. If a whitepaper claims partnerships with specific companies or integration with specific protocols, verify those claims independently. If the whitepaper references "our successful mainnet launch in Q3 2024" but there's no on-chain evidence of a launch, or if the claimed partner has no public mention of the partnership, these are fabrications.
Method 5: Image and Diagram Reverse Search
Save any diagrams or technical architecture images from the whitepaper. Run them through Google Image Search (images.google.com, then upload the image). If the "original" technical architecture image returns results from another project, the technical claims may be copied wholesale — not just the text. Many fake whitepapers use legitimate diagrams from other projects with only the project name changed.
Method 6: Tokenomics Math Verification
Add up all the percentages in the tokenomics table. They must total exactly 100%. Calculate: total supply × each percentage = expected tokens per category. Verify these numbers are internally consistent. A whitepaper where the percentages don't add to 100%, or where claimed token amounts are inconsistent with stated total supply, indicates either careless writing (unprofessional) or deliberate obfuscation (concerning).
Method 7: Roadmap Plausibility Check
Calculate the implied development velocity. If a 5-person team plans to: build a mainnet, launch a DEX, create a mobile wallet, complete three enterprise partnerships, and list on 10 exchanges — all in 6 months — the roadmap is fictional. Use GitHub (if the project has a public repo) to assess actual development activity vs. claimed progress.
Method 8: Legal Document Completeness
Any legitimate whitepaper includes a disclaimer/risk section, terms of use, and clear token sale terms. Generic or missing legal sections — or legal sections that are obvious copies of Ethereum or Bitcoin white papers with find-replace substitutions — indicate either no proper legal counsel or deliberate copying. See our presale phishing and scam detection guide for additional document fraud signals.
Method 9: GitHub Activity Check
If the whitepaper references technical development, verify on GitHub. Check: does the project have a public repo? How many commits are there? When was the last commit? Are commits from multiple developers (indicating real team) or all from one account (solo project or outsourced)? Empty or recently created repos with no history for projects claiming months of development are major red flags.
Method 10: Competitor Comparison
Find 2-3 projects solving the same problem. Read their whitepapers alongside the one you're evaluating. Does the evaluated project's technical approach actually differ from existing solutions, or does it essentially describe the same solution with different branding? A whitepaper that can't articulate a specific, concrete differentiation from existing solutions — beyond "faster, cheaper, more scalable" — has no genuine competitive analysis. See our presale risk evaluation guide for complete evaluation methodology.
Red Flags Summary
- Plagiarised text discovered via Copyscape
- AI-generated content detected via GPTZero
- Team cannot answer technical questions from their own whitepaper
- Tokenomics don't add to 100% or are mathematically inconsistent
- Roadmap requires unrealistic development velocity for team size
- No GitHub repository or empty repository for claims of months of development
- Architecture diagrams that reverse-search to other projects
- Missing risk disclosure or generic legal section
For additional fraud protection beyond whitepaper analysis, see our smart contract audit guide.
Glossary
- Plagiarism
- Copying text or ideas from another source without attribution and presenting them as original. Detected via text comparison tools like Copyscape.
- AI-Generated Content
- Text produced by AI language models (ChatGPT, Claude) without substantive human expertise. Detectable via tools like GPTZero. Not inherently fraudulent but concerning when masking absent technical knowledge.
- Technical Vagueness
- Using impressive-sounding technical terminology without specific implementation details — indicating the team wrote about technology they don't understand.
Disclaimer
Important: Even detailed, original whitepapers can accompany fraudulent projects. Whitepaper quality is one signal among many. This article is educational only. CryptoPresaleNews.com is not a licensed financial advisor.
