0x Protocol Token (ZRX) — 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 0xc6F348dd3B91a56D117ec0071C1e9b83C0996De4: 10.0441 WETH of depth, 0% of its LP supply burned
- Uniswap V2 USDC pool at 0x9f65DF828d21C8860ee1499dA6397D50d85E14a0: 4.4508 USDC of depth, 0% of its LP supply burned
- Uniswap V2 USDT pool at 0x05556053D0966c7701201A2103dcb56CF75BdD92: 1,920 USDT of depth, 0% of its LP supply burned
- SushiSwap WETH pool at 0x0BC5AE46c32D99C434b7383183ACa16DD6E9BdC8: 0.0448 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.