Amp (AMP) Smart Contract Risk
ERC777 Transfer Hooks (Reentrancy Risk)
⚠ HIGH severityVulnerability
AMP implements ERC777 transfer hooks (tokensReceived/tokensToSend), enabling reentrancy attacks on every token transfer. The infamous imBTC/Uniswap reentrancy exploit used this vector.
Related: Reentrancy Attack
Safe integration
Apply reentrancy guards (nonReentrant modifier) on all functions that interact with ERC777-compatible tokens. Use checks-effects-interactions pattern.
Contract addresses
| Chain | Address |
|---|---|
| Ethereum | 0xff20817765cb7f73d4bde2e66e067e58d11095c2 |
Audit any contract that interacts with AMP: SmartContract.us automatically detects AMP integration risks →
Chain & standard security guides
What this contract permits today
Read live from Ethereum on 2026-10-14. This is a different question from the integration risk above: not how to call the token safely, but what the holders of its keys are able to do to the people holding it.
| Question | Answer |
|---|---|
| Can new tokens be created? | No |
| Can transfers be blocked? | No |
| Is there a trading tax? | No |
| Can the logic be replaced? | No |
| Can liquidity be withdrawn? | Yes |
The permissions above rest with 0x533a36b5e56C1f0361a53d4395F4F0c5f1AD63f8, itself a contract, which may be a multisig or a timelock. Whether that is acceptable depends on who holds it.