Basic Attention Token (BAT) — 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?
New tokens can be created after deployment.
Whoever holds that permission can increase the supply, which reduces the share each existing token represents.
- createTokens()
Whether minting has been used, and under what constraints, is not established here.
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 0xB6909B960DbbE7392D405429eB2b3649752b4838: 25.9845 WETH of depth, 0% of its LP supply burned
- Uniswap V2 USDC pool at 0x02DD9Ff64EeC5D866a512EF08463C7c85A14e4Aa: 38.9121 USDC of depth, 0% of its LP supply burned
- Uniswap V2 USDT pool at 0x0c11F54ec778Cdf062Ad0d8464cC7b7C9108c934: 32.0317 USDT of depth, 0% of its LP supply burned
- SushiSwap WETH pool at 0x998BF04788C1c631C0e02BD1eED3D945308Bf0a3: 0.0699 WETH 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.