Discussions

Hello GoPlus team. Your token security API now flags Zaibatsu Wagies (ZAIBATSU) on Robinhood Chain (chain 4663, contract 0x5DBaCA8327B0bAA57eB6C872a333Bf8D6F642BA3) as a honeypot, together with hidden owner, transfer pausable and owner can change balance. On Oct 11, 2026 the same API returned is_honeypot=0. The token is not a honeypot: 9 different wallets sold it in the last 15 hours, for example these sell transactions:

0x23a2dcda581f1f3c999dcdd3181c6f61111b4baacc7c5e150c620f1d858b6747 (250M ZAIBATSU sold for 12.39 GME)

0x8b1533dcba93691e180d5f0355c1e4c37bd002e3939633593f5ba9aeee958471 (68.45M ZAIBATSU sold for 3.42 GME)

0xbb5b4373185026f14fc8bdcd4cbbe2622921324ae93b4f9b6cbadf4bacd074c4 (30.69M ZAIBATSU sold for 1.54 GME)

Likely cause one: the token is a standard Doppler DERC20 (Solady ERC20) with a built-in infinite Permit2 allowance. approve(Permit2, amount) reverts with Permit2AllowanceIsFixedAtInfinity() for any amount other than the max uint256, by design. A sell simulation that approves Permit2 for an exact amount fails at that step. Real wallets do not need that approval, which is why real sells go through.

Likely cause two: your dex list for this token only contains third-party ZAIBATSU/USDG pools with 4.99% to 99% LP fees and $0.2 to $46 of liquidity. The real market is the Doppler pool 0x1cbac474c81b584caff0f1aa23eb38fb39beab5c173eb6d8486036f4f29808ca (ZAIBATSU/GME, hook 0x4e3468951D49f2EEa976eD0D6e75fFCb44a9a544, about $77k of liquidity).

The other flags are also false. owner() is the Doppler Airlock contract 0xeb7C034704eF8Dcd2D32324c1545f62fB4aD0862, not a team wallet. controller() can only call disableBalanceLimit(), and the anti-whale limit already expired on Aug 4, 2026. lockPool() only blocks transfers to the placeholder address 0xdeaDDeADDEaDdeaDdEAddEADDEAdDeadDEADDEaD, so trading is not affected. There is no mint, burnFrom or any other function that lets the owner change balances.

The token is listed on CoinGecko: https://www.coingecko.com/en/coins/zaibatsu-wagies

Please re-scan the token and remove the honeypot flag. Thank you!