Discussions

Discussions

Ask a Question
Back to all

Frong on Robinhood listed as honeypot is WRONG

2 days ago by KR

Title: False positive flags on FRONG (Robinhood Chain), Uniswap UERC20 template

Hi GoPlus team,

Token Security flags FRONG on Robinhood Chain (chain ID 4663) as a honeypot, with a hidden owner and owner-can-change-balance. I believe all three are false positives caused by the standard Uniswap token template it launched with.

Token: 0x6245e67affA44a23077f0Ea7f981a8DC743a0c47
Main pool: Uniswap v4 ETH/FRONG, pool ID 0xacea8920877840033f0275c37f9b61550b5326917e948bcf8339714d96f9521a

  1. FRONG was launched on pools (pools.trade / pools.xyz), Uniswap's launchpad on Robinhood Chain. It deploys tokens from Uniswap's UERC20Factory (0x000000e200088D55C39a11F609E5F667729ad49b) into a hookless native-ETH v4 pool. Source: https://github.com/Uniswap/uerc20-factory

  2. UERC20 is a fixed-supply Solady ERC20, minted once in the constructor. It has no owner or admin role, no mint after deployment, no pause, no blacklist and no tax. "creator" is an informational immutable with no permissions.

  3. Solady gives the canonical Permit2 contract (0x000000000022D473030F116dDEE9F6B43aC78BA3) a fixed infinite allowance. transferFrom skips the allowance check when Permit2 is the caller, and approve(Permit2, amount) reverts unless amount is max uint256. This is probably what reads as a hidden owner or balance control, and it would make a simulated sell fail if the simulator approves Permit2 for an exact amount.

  4. Selling works in practice: on 26 Oct 2026, DEX Screener showed 321 sells from 181 different wallets over 24 hours.

Every token launched through pools likely uses this template, so the same flags probably affect all of them. Could you re-check FRONG and consider recognising the UERC20 template?

Thanks