OMGToken (OMG) — what its owner can do

Ethereum · 0xd26114cd6ee289accf82350c8d8487fedb8a0c07
Read from the chain on 2026-10-14. All checks completed.

Who can do these things

The permissions above rest with 0x000000000000000000000000000000000000dEaD, a single private key rather than a multisig or a timelock. Whether that is acceptable depends on who holds it.

  • 0x000000000000000000000000000000000000dEaD — a single private key, 0 transactions sent. Found via owner().

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

Present

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.

  • mint(address,uint256)
  • mintTimelocked(address,uint256,uint256)

Whether minting has been used, and under what constraints, is not established here.

Present

Can transfers be blocked?

Transfers can be blocked by whoever holds the relevant permission.

If the mechanism is applied to your address, or to the pool you would sell into, you would be unable to sell.

  • Pause controls: unpause(), pause()
  • paused() currently returns false

This reports what the contract permits. Whether any address is currently blocked was not checked.

Not present

Is there a trading tax?

No trading tax mechanism was found.

  • No tax setter or tax rate in the ABI
Not present

Can the contract logic be replaced?

The contract logic is fixed and cannot be replaced.

  • No proxy pattern detected in the deployed bytecode
Present

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 0x48E313460DD00100e22230e56E0A87B394066844: 0.4237 WETH of depth, 0% of its LP supply burned
  • Uniswap V2 USDT pool at 0x759374b8eae5d148C62f3995204AF243bf11E541: 5.00e-5 USDT of depth, 100% of its LP supply burned
  • SushiSwap WETH pool at 0x742c15d71eA7444964BC39b0eD729B3729ADc361: 0.5617 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.

This is not advice, and it is not complete. It reports what the contract allows and who can act on it. It cannot tell you whether anyone intends to. Treat a clean report as the absence of one kind of evidence, not as a recommendation.

Check another

← Back to the checker