Novaquill

Blog · 2026-11-18

Detect honeypot tokens on BNB Chain and Base programmatically (simulation, not heuristics)

Most honeypot checks read the contract: look for a _taxFee variable, a blacklist mapping, a tradingEnabled flag. Scam contracts adapt to whatever is popular to check. The only robust test is the one the victim runs: buy, then try to sell. You can do that without spending anything, with eth_call and state overrides.

The trick: run a helper contract that doesn't exist

eth_call accepts a third parameter, a state override, that lets you place arbitrary bytecode and balance at any address for the duration of the call. Deploy nothing, just override:

const res = await client.request({ method: 'eth_call', params: [
  { to: SIM, data: encodeFunctionData({ abi, functionName: 'sim', args: [router, token, parseEther('0.05')] }), gas: '0x1c9c380' },
  'latest',
  { [SIM]: { code: simRuntimeBytecode, balance: '0x56bc75e2d63100000' } },
]});

Inside sim:

  1. Quote getAmountsOut(ethIn, [WETH, token]).
  2. Buy with swapExactETHForTokensSupportingFeeOnTransferTokens. The difference between quote and balance received is the real buy tax.
  3. Transfer 10% to a fresh address: catches transfer taxes and transfer blocks.
  4. Approve the router, quote the sell, sell with swapExactTokensForETHSupportingFeeOnTransferTokens. Quote versus ETH received is the real sell tax. A revert here, after a successful buy, is a honeypot.

Wrap each step in try/catch so you learn which step failed. Public BNB Chain and Base RPCs accept state overrides; a full simulation takes about half a second.

What simulation can't see

Or use the API

We run all of the above as an API: GET https://novaquill.dev/api/v1/token?chain=bsc|base&address=0x… returns a JSON risk report (score 0-100, flags such as HONEYPOT, HIGH_SELL_TAX, OWNER_CAN_MINT, LP_NOT_LOCKED, simulation numbers, liquidity, owner holdings).

There is also a feed of new launches, each already scanned, as JSON at /api/v1/launches.