OmiseGO (OMG) Smart Contract Risk
Missing Return Data
⚠ HIGH severityVulnerability
OMG token does not return a boolean on transfer, violating the ERC20 standard interface.
Related: Unchecked Return Values
Safe integration
Use OpenZeppelin SafeERC20 (safeTransfer) to handle non-standard return values.
Contract addresses
| Chain | Address |
|---|---|
| Ethereum | 0xd26114cd6ee289accf82350c8d8487fedb8a0c07 |
Audit any contract that interacts with OMG: SmartContract.us automatically detects OMG 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? | Yes |
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.