Blacklist function

A blacklist function is a piece of code in a token's smart contract that lets a privileged address, usually the owner, flag specific wallets as banned. Once a wallet is on the list, the contract refuses its transfers, which in practice means it cannot sell, move, or sometimes even receive the token.

Mechanically, the contract keeps a mapping of addresses to a true or false flag, and the transfer logic checks that flag before letting tokens move. The owner calls something like addToBlacklist or setBots to switch the flag on. On EVM chains this is plain Solidity anyone can read on a verified contract, though the function names are often disguised. Some legitimate assets have similar controls: major fiat-backed stablecoins can freeze addresses tied to hacks or sanctions, and Solana tokens can carry a freeze authority that does the same job at the account level.

For holders of small tokens, the problem is who holds the switch. A blacklist in the hands of an anonymous deployer can turn any token into a honeypot for chosen wallets, often anyone who bought early enough to profit. Projects sometimes justify it as protection against sniper bots at launch, and that can be true, but the same power can be used against ordinary buyers at any time.

Check the verified source for any mapping that blocks transfers, and look at whether ownership is renounced or held by a multisig with a timelock. On Solana, see whether the freeze authority has been revoked. Token scanners flag blacklist functions automatically, but they can miss renamed or obfuscated versions, and a proxy contract can add one later through an upgrade.