imBTC (imBTC) Smart Contract Risk
ERC777 Transfer Hooks (Reentrancy Risk)
⚠ HIGH severityVulnerability
imBTC is an ERC777 token with transfer hooks that enable reentrancy. This was the exact vector used to drain ~$300K from Uniswap V1 in April 2020.
Related: Reentrancy Attack
Safe integration
Apply reentrancy guards on all functions that transfer or receive ERC777 tokens. Never call external contracts before updating state.
Contract addresses
| Chain | Address |
|---|---|
| Ethereum | 0x3212b29e33587a00fb1c83346f5dbfa69a458923 |
Audit any contract that interacts with imBTC: SmartContract.us automatically detects imBTC 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? | Yes |
| Can transfers be blocked? | Yes |
| Is there a trading tax? | No |
| Can the logic be replaced? | No |
| Can liquidity be withdrawn? | No |
The permissions above rest with 0xb9E29984Fe50602E7A619662EBED4F90D93824C7, a single private key rather than a multisig or a timelock. Whether that is acceptable depends on who holds it.