Rug pull vs honeypot: understand the difference
Learn how honeypot mechanics differ from liquidity, supply and creator-distribution rug-pull conditions—and what evidence can reveal each one.
A honeypot is an exit mechanism
A honeypot typically permits buying while blocking, restricting or economically punishing selling. Evidence may appear in sell simulations, transfer logic, blacklists, trading switches, configurable taxes or upgradeable implementation code.
A rug pull is a broader failure pattern
Rug-pull risk can involve liquidity withdrawal, privileged minting, concentrated supply sales, hidden allocation control or coordinated creator-wallet distribution. The investor outcome may be similar even when the token remains technically sellable.
The evidence sets overlap
Owner powers and upgradeability can enable either behavior. Liquidity, holders and wallet flows provide market context that a contract-only honeypot test cannot. That is why a green sellability result should not end the review.
Use different checks for different claims
For honeypot risk, prioritize executable sell evidence, fees and transfer controls. For rug-pull conditions, add LP ownership, lock terms, supply authority, initial allocation, holder clusters and creator-linked flows.
Neither label predicts intent
Automated tools observe conditions and behavior. They cannot prove a person's identity, private agreement or future intent. Report the mechanism, source and uncertainty instead of treating a score as an accusation or guarantee.