What is a honeypot token?

A honeypot token is a crypto contract deliberately written so buy transactions succeed but sell transactions fail or are taxed at close to 100%. It looks like a normal token, it shows up in your wallet, the price chart moves, other people appear to be trading it, right up until you try to sell and the transaction won't go through.

How the honeypot trap actually works

Most ERC-20 and BEP-20 tokens use a standard transfer function that any wallet can call. A honeypot modifies that function with extra logic, often something as simple as an if statement that checks whether the sender's wallet matches a hardcoded list of allowed addresses. If it doesn't, the sell either reverts outright or gets hit with a fee set so high (sometimes literally 100%) that nothing is actually received. The developer's own wallets are usually on that allowed list, so they can sell freely while everyone else can't.

This is one specific way a token can turn into a rug pull, distinct from a liquidity pull, which drains the trading pool instead of blocking individual sells. Both leave holders unable to get their money out, through different mechanisms.

Why buy transactions still work

The whole trap depends on buys succeeding. If purchases failed too, nobody would put money in and there'd be nothing to trap. So the restriction is written to trigger only on the sell side, on outgoing transfers from a holder's wallet, not incoming ones. This is also why a rising price chart or visible buy volume tells you nothing about whether a token is a honeypot; those signals only reflect the side of the contract that was never restricted in the first place.

How to check a token for a honeypot before you buy

A honeypot checker simulates both a buy and a sell transaction against the live contract, without spending real funds, and reports whether the simulated sell actually completes. Paste the contract address into our free token checker and it runs this simulation alongside checks for unlocked liquidity, unlimited mint functions, and unrenounced ownership, the same underlying pattern that shows up around most honeypots, in one report.

For a broader walkthrough of contract-level checks beyond just the sell simulation, see our guide to checking if a token is safe.

Other signs to check alongside the sell simulation

The sell simulation is the most direct test, but a few other contract details tend to show up alongside honeypots and are worth checking at the same time:

• Asymmetric buy and sell tax. A small, equal tax on both sides is normal on many tokens. A tax that's low or zero on buys but extremely high on sells is a common honeypot pattern, since it lets the price chart look active while quietly blocking exits.
• Unverified source code. If the contract isn't published on the block explorer, the hidden logic that blocks sells can't be read by anyone outside the development team, which is often the point.
• A very new or unfamiliar contract. Honeypots are typically deployed fresh for each scam rather than reused, since a flagged contract address gets shared quickly once holders find they can't sell.

None of these alone confirms a honeypot, but a token showing several of them together, on top of a failed sell simulation, is a strong signal to walk away rather than investigate further.

When a failed sell isn't a honeypot

A few legitimate scenarios can also cause a sell to fail or come back much smaller than expected:

• Slippage set too low. Low-liquidity tokens can move price enough between submitting and confirming a trade that a tight slippage setting causes a revert. Raising slippage slightly (not drastically) can resolve this on a genuine token.
• A disclosed, high sell tax. Some legitimate tokens charge a real sell tax, sometimes 10% or more, that's stated in their documentation and visible in the contract. The transaction still completes, you just receive less than expected. That's a design choice to be aware of, not a hidden trap.
• Network congestion. Gas price spikes can cause any transaction, buy or sell, to fail if the gas limit is set too low. This affects the whole network, not one specific token.

The distinguishing factor is whether the restriction is disclosed and applies predictably, versus hidden and total. A honeypot checker's simulation cuts through the ambiguity by testing the actual contract logic directly.

FAQ