GGlossary · 2 min read

What is a honeypot token?

A honeypot token lets you buy but blocks selling, using contract logic rather than market conditions. How the trap works and how to test for it first.

303 words · about 2 minutes·Article updated 20 August 2026
Definition

A honeypot token lets you buy but stops you selling. The contract accepts incoming transfers and reverts outgoing ones, through a transfer restriction, a wallet blocklist, or a sell fee set so high no exit succeeds. The pool looks ordinary; the token contract is the trap.

The signature is asymmetry rather than price. Buys confirm, sells revert with an error, and the holder count only ever climbs. The standard test is simulating a sell before committing a buy — routing a small exit through the same pool to see whether it would succeed at all.

A liquidity lock does not address this, because the pool is not what blocks you, and neither does the absence of a rug pull: nothing has to be drained when nothing can leave. Read the token contract's transfer rules separately from the pool's lock state.

A lock guarantees exactly one thing: the pool cannot be withdrawn before the release date. Not the price, not the team, not the token. A locked pool can still fall.
Where you'll see it on Locksley

Every token page links the token contract and renders its trade history, where a buys-only pattern shows in the sell column. Locksley reports mechanisms and does not label any token a honeypot; Explore is the screener for comparing pools.

Honeypots: how they work covers the contract patterns, and I can't sell my token walks the diagnosis when a sell has already failed.

Frequently asked questions

Is a honeypot the same as a sell that fails from slippage?

No. A slippage failure is a market condition: the price moved past your tolerance, and raising it or splitting the order usually gets the trade through. A honeypot is contract logic — the sell reverts at any tolerance, at any size, for every wallet the rules exclude. Retrying never helps.

FiguresEvery number on this page is frozen at the date printed beside it and refreshed when the page is rebuilt — not live. The sentences reason about the figures, so a value that changed underneath them would make the prose wrong. Live values live on Explore and the pages it links out to. Methodology →
CorrectionsFound something wrong? Send the page and what you computed instead through the contact page. Every correction is logged publicly.
ReusePublished under CC BY 4.0. Quote it, translate it, fork it — cite the page and the date.
Who wrote thisWritten and maintained by the Locksley editorial team. Locksley is built by TrustSwap, which also owns Team Finance — the tool linked above.