You're here because you're tired of getting rugged, sybil-flagged, or both. Good.

Here's how to get the most out of your membership:

🎓 Start the Course

Work through the modules in order. Each lesson builds on the last — from identifying rug pull mechanics to building a sybil-resistant on-chain identity that actually qualifies for airdrops.

💬 Use the Chat

Drop your due diligence questions, share suspicious contracts you've found, or flag protocols you're farming. This is a working group, not a spectator sport.

📋 The RPRF Checklist

Module 5 gives you a complete due diligence system. Print it. Use it on every project before you ape in.

Ground Rules

• No sharing wallet addresses publicly (opsec matters)

• No promoting projects without running them through the checklist first

• Help each other. The best alpha comes from the community

Your first assignment: go to Module 1, Lesson 1 and complete the 5-Minute Smart Contract Red Flag Audit on any token you're currently holding.

Let's get to work.

I've analyzed over 40 rug pulls from the past 12 months. The same five patterns showed up in nearly every single one — usually days before the pull happened. Here's what to look for.

1. Concentrated Token Holdings With Fresh Wallets

When 60%+ of supply sits in wallets created within the past 30 days, that's not "early investors." Run the top holders through Arkham or Nansen. If the wallets have zero history before the mint — red flag.

2. Liquidity That Can Be Pulled in a Single Transaction

Check if LP tokens are locked. If they're sitting in an EOA (externally owned account) instead of a time-lock contract, the dev can drain the pool in one tx. Tools: DexScreener liquidity tab, GeckoTerminal pool explorer.

3. Unrenounced Contract Ownership With Mint Functions

If the contract owner hasn't renounced AND the contract has an active mint function, they can inflate supply to zero out your position. Check on Etherscan → Read Contract → look for owner() returning a non-zero address, then check Write Contract for mint().

4. Social Proof That Doesn't Trace Back to Real People

Fake KOL endorsements are cheap. Before trusting a "partnership" announcement, verify: Does the KOL's actual account mention it? Do team LinkedIn profiles have connection history older than 6 months? Are the Telegram admins' accounts older than the project?

5. Sudden Tokenomics Changes Post-Launch

If a project modifies tax rates, transfer limits, or blacklist functions after launch — especially via a proxy contract upgrade — that's the clearest exit signal. Set up contract event alerts via Tenderly or OpenZeppelin Defender.

The Pattern

Most victims see one of these flags and rationalize it. The rug happens when 3+ are present simultaneously.

I teach a full system for running this analysis in under 10 minutes per project inside Rug Pull Red Flags. But this post alone should save you from the obvious ones. Stay sharp.