Compound (COMP) — what its owner can do
Who can do these things
No privileged address could be identified. This is not the same as there being none — see the limitation below.
Only named getters were read. If this contract uses role-based access control without enumeration, its role holders cannot be listed, and the absence of a controller here does not mean there is none.
What the contract permits
Can new tokens be created?
The supply is fixed. No function exists to create new tokens.
- No mint entry point in the contract ABI
Can transfers be blocked?
No mechanism was found that would let anyone block a transfer.
- No address blocking, pause, trading switch or transfer cap in the ABI
Is there a trading tax?
No trading tax mechanism was found.
- No tax setter or tax rate in the ABI
Can the contract logic be replaced?
The contract logic is fixed and cannot be replaced.
- No proxy pattern detected in the deployed bytecode
Is the liquidity locked?
The trading liquidity can be withdrawn by whoever holds the LP tokens.
Withdrawing liquidity leaves holders with tokens and no pool to sell them into. This is the mechanism behind most losses described as rug pulls.
- Uniswap V2 WETH pool at 0xCFfDdeD873554F362Ac02f8Fb1f02E5ada10516f: 30.7426 WETH of depth, 0% of its LP supply burned
- Uniswap V2 USDC pool at 0x6F81d90E771B551451382b4c8B41C86B978d3420: 3.4941 USDC of depth, 0% of its LP supply burned
- Uniswap V2 USDT pool at 0x942Be9e8a12cFAAF997Cd266487Eaf8553B119d2: 0.7492 USDT of depth, 0% of its LP supply burned
- SushiSwap WETH pool at 0x31503dcb60119A812feE820bb7042752019F2355: 18.8827 WETH of depth, 0% of its LP supply burned
- SushiSwap USDC pool at 0x6f908e82E94e088f726e456E3403aAa00723e6e3: 1.24 USDC of depth, 0% of its LP supply burned
Who holds the unburned LP tokens cannot be established: ERC20 holders cannot be enumerated over RPC. It may sit in a time-lock contract, or in a wallet, and this check cannot tell those apart.