Advanced Verification Techniques

GitHub Repository Analysis

• Check commit history (look for consistent development)

• Verify repository age matches claimed project timeline

• Watch for recently cloned repos (common scam tactic)

• Look for meaningful commits (not just README updates)

  • If you're not a dev, politely ask one to check for you.

  • We have several developers in our private TG groups.

• Examine contributor profiles for legitimacy

Identity Red Flags

Common Impersonation Patterns

• Dev Name Pattern: Almost everyone with "dev" in their name on X or TG is fake

• AI-Generated Photos: Overly earnest, perfect-looking human photos are typically fake

  • Look for subtle asymmetries in facial features

  • Check background consistency and unnatural lighting

  • Be skeptical of "too perfect" professional headshots

  • People often even use other people's photos for their PFP or X posts

    • Make sure to reverse image search photos and verify authenticity of photos

    • If you see an image is recycled from the web, be cautious

Cross-Platform Verification

• Never Trust Single-Channel Verification:

  • LinkedIn profiles are easily faked

  • GitHub accounts can be newly created

  • X profiles can be purchased

  • Seemingly elite, clean X handles like "capsule" can also be purchased

  • Telegram accounts can be renamed

• Multi-Channel Authentication:

  • Cross-reference identities across multiple platforms — as many as you can

  • Check account creation dates across platforms

  • Look for consistent posting history and style

  • Verify mutual connections independently

  • Pro tip: work for your bags and DM the founder directly on another channel to verify authenticity

    • People will often (not always) use the same @ handle for their X as they use on TG

• Image Verification:

  • Reverse image search profile pictures

  • Check for stock photo watermark removal

  • Look for consistent image usage across platforms

  • Be extra skeptical of "professional" headshots

Common Deception Tactics

• Purchased X accounts with manufactured history (often RTs or tweets unrelated to web 3)

• AI-generated team photos and videos

• Fake "team at work" environments

  • Fake dev scammers love posting coffeeshop photos that are easily found on reverse google image search

• Stolen credentials from legitimate but lesser-known professionals

• Manufactured GitHub commit histories

• Purchased positive testimonials and endorsements

• Important: scammers often have mutual followers or even notable followers.

  • These are bad actors who have played the long game and seeded follows over time from notable accounts by @ replying to their tweets.

  • For instance, these accounts can get follows from the likes of pmarca (famous VC), toly (founder of solana), or other notable influencers.

  • If they are followed by someone very selective with who they follow like Vitalik, Elon, etc. you can ape with more conviction.

  • If they're followed by other trenchers, it could be (likely is) due to the fact that they've scammed before and the trenchers never unfollowed them.

Remember: with any launchpad token or newly launched project, assume identity fraud until proven otherwise.

Content Authentication

• Be skeptical of AI-generated videos (increasingly common)

• Watch for Eleven Labs voice synthesis in Twitter Spaces

• Examine code quality beyond surface appearance

• Test functionality personally (don't trust demos alone)

• Verify revenue claims with concrete evidence (rare but powerful)