FLAPPY returned 90/100 on the quick public-risk scan.
Deeper TokenToolHub contract intelligence returned 65/100.
Contract:
0x2Ac4169b21b1CBb2b9fA30cDB4fE1A71b8087777
Network: BNB Smart Chain
Token:
Flap Mascot (FLAPPY)
The source is verified and trading simulation did not detect a honeypot.
Simulation results:
• Honeypot: Not detected
• Buy tax: 3.00%
• Sell tax: 2.97%
However, deeper contract analysis identified 3 material risk scenarios:
• Possible supply dilution
• Possible implementation replacement
• Possible generic execution abuse
Detected control surfaces include:
• Supply expansion
• Supply reduction
• Upgrade authority
• Generic external execution
• Asset recovery/withdrawal
The available analysis did NOT detect:
• Mutable fee-setting capability
• Trading switches
• Wallet restrictions
• Emergency pause
One of the most important findings is the authority structure.
The live owner() call returned:
0x0000000000000000000000000000000000000000
So ownership is currently renounced.
But the contract is also upgradeable.
Resolved implementation:
0xae562c6a05b798499507c6276c6ed796027807ba
The proxy administrator could not be resolved.
This means “ownership renounced” does not necessarily answer every authority question.
If a separate proxy administrator retains the ability to replace the implementation, the logic users interact with today may still be changeable.
The verified code also exposes supply-expansion capability and generic execution paths.
Those findings do not establish malicious intent.
They identify trust assumptions that should be verified:
Who controls the upgrade path?
Who can exercise mint capability?
Is supply technically capped?
Is the upgrade administrator protected by multisig, timelock or governance?
Full FLAPPY contract intelligence:
https://tokentoolhub.com/token-safety-checker/?net=bsc&address=0x2Ac4169b21b1CBb2b9fA30cDB4fE1A71b8087777
#BNBChain # #CryptoSecurity #Onchain #Web3