The 7 Red Flags of a Memecoin Honeypot

Honeypot contracts have evolved past the obvious "transfer reverts" pattern. Modern traps look clean to a casual reader, pass a few automated checks, and only spring on retail at the dump. These are the seven patterns we see most often in memecoin honeypots flagged by GoPlus + our own simulation.

1. Asymmetric tax

1% buy tax, 99% sell tax. Or 5% buy, sell-tax modifiable by owner. The contract will report a low fee at deploy, then escalate after liquidity is in. We flag any contract where sell tax can be raised without a timelock.

2. Hidden mint

An owner-only `_mint()` call wrapped in a misleadingly-named function (e.g. `claim`, `airdrop`, `seedRewards`). Total supply on Etherscan looks fixed; in practice the deployer can dilute at will.

3. Blacklist

An `_isBlacklisted` mapping the owner can set. Once your wallet is on the blacklist, the contract reverts your sells. You can buy, you can hold — you can't exit. Pulsentric flags contracts with arbitrary-blacklist callable by an EOA owner.

4. Anti-bot turned anti-retail

Many tokens ship with `tradingActive = false` at deploy as legitimate anti-MEV protection. But if `tradingActive` can be flipped back to `false` after launch, it's not anti-bot — it's a freeze switch. Same applies to `maxTransactionAmount = 0` patterns.

5. Proxy + mutable implementation

If the contract is a transparent proxy and the admin can swap the implementation without governance, the entire token logic can change overnight. "Verified source" on the proxy means nothing if the implementation is upgradable by a private key.

6. Fake liquidity lock

LP tokens "locked" via a custom contract no one has audited. Real locks go through Unicrypt, Team.Finance, Pinksale, or are burned to 0x…dead. Custom lockers are often configurable to release on a hidden trigger.

7. Pre-funded sniper wallets

Token launches with 5-10 wallets each holding 1-3% of supply, all funded from the same source within 24 hours of deploy. These wallets are the dump. Top-holder concentration analysis catches them; sequencing analysis confirms the source.

Each of these patterns is checkable in seconds. The combined check is what Pulsentric automates — paste a contract into /scanner for the live audit.