Honeypot checker and token safety check
Paste an ERC-20 contract address and pick a chain. The checker simulates a transfer from the largest holder to see whether the token can be moved, measures how concentrated the supply is, and reads ownership and proxy status straight from the chain. It works on all 17 EVM chains NodeFlare runs, including Robinhood Chain, Ink and Zircuit. Read-only: no wallet connection, no sign-up.
What the checker reports
- Transfer simulation: a simulated transfer() from the largest sampled holder. A transfer that fails is the mark of a possible honeypot.
- Holder concentration: the share of supply held by the largest holder and by the top ten of the sampled holders.
- Ownership: whether an owner still controls the contract, and the owner address when there is one.
- Upgradeable proxy: whether the token's logic sits behind a proxy that an admin can replace.
- Is a contract: whether the address holds code at all. A plain wallet address posing as a token is a red flag.
- Risk score and signals: 0 to 100, higher is riskier, with every signal that counted listed next to it.
What it does not tell you
The transfer simulation is an indicator, not a verdict. It does not buy and sell through a DEX, so it does not measure buy or sell tax, and it cannot see whether liquidity is locked. A token with no risk signals can still lose its value. Use the result as a first filter before you approve or trade a token, and check what a token may already spend from your wallet with the token approval checker.
Supported chains
Ethereum (1), Base (8453), BNB Chain (56), Arbitrum One (42161), Optimism (10), HyperEVM (999), Avalanche (43114), Unichain (130), Sonic (146), Polygon (137), Zircuit (48900), Robinhood Chain (4663), XLayer (196), Soneium (1868), BOB (60808), Ink (57073), Mode (34443).
Honeypot checker: questions and answers
What does the honeypot checker do?
You paste an ERC-20 contract address and pick a chain. The checker reads the token from a NodeFlare node: whether the address is a contract, who owns it and whether ownership is renounced, whether it is an upgradeable proxy, how much of the supply the largest holders have, and whether a simulated transfer from the largest holder goes through. Each finding that counts as a risk is listed, and together they make a risk score from 0 to 100, where higher is riskier.
How does it detect a honeypot?
It simulates transfer() from the token's largest sampled holder with an eth_call, so nothing is sent and no wallet is needed. If that transfer reverts or returns false, the token may block ordinary holders from moving it, which is how a honeypot traps buyers. This is an indicator and not proof: the largest holder can be a pool or router that is exempt from limits, and some legitimate tokens reject a one-unit transfer. It does not simulate a buy and a sell on a DEX, and it does not measure buy or sell tax.
Which chains are supported?
All 17 chains NodeFlare runs nodes for: Ethereum, Base, BNB Chain, Arbitrum One, Optimism, HyperEVM, Avalanche, Unichain, Sonic, Polygon, Zircuit, Robinhood Chain, XLayer, Soneium, BOB, Ink, Mode. That includes young chains such as Robinhood Chain, Ink, Zircuit, Soneium, BOB and Mode, where new tokens appear before most scanners list them.
What does the risk score mean?
The score adds up the risk signals that were found: a non-contract address, no readable name, ownership that is not renounced, an upgradeable proxy, a largest holder with half the supply or more, a failed transfer simulation and a very recent first transfer. A score of 0 means none of these were found. It does not mean the token is safe: liquidity can still be pulled and a holder can still sell.
Why are the holder figures sometimes shown as a minimum?
Holders are found from the token's Transfer events. On chains that limit how far back a log query may go, and for tokens with very many transfers, only recent blocks are scanned, so the sample can miss older holders. The percentages are then a lower bound and are marked with ≥. When no holder could be sampled, the transfer simulation is shown as inconclusive rather than as passed.
Is ownership renounced always safe?
No. Renounced ownership removes one way to change a token after launch, such as raising a tax or pausing transfers. It does not rule out a trap written into the contract, liquidity being removed, or a large holder selling. Established stablecoins and wrapped assets are not renounced by design; the checker does not count that against tokens on its list of established tokens.
Can I run this check from code?
Yes. The same check is one POST to the NodeFlare Token Safety API with an API key; the free plan includes it. The response has the same fields this page shows, as JSON.
More free tools: token approval checker, multi-chain wallet viewer and gas price comparison.
Run the check from your own code
The Token Safety API returns the same result as JSON in one POST, on all 17 chains. The free plan includes it.