0xf2b688b2201979d44fdf18d1d8c641305cf560ba
As of 21 Nov 2026, Trustblock’s record holds 0xf2b688b2201979d44fdf18d1d8c641305cf560ba on BNB Chain as a contract of Devomon. 1 audit report on Trustblock lists this address: CertiK, 18 Jan 2024. 3 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on BNB Chain.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| Devomon.io (Audit) | CertiK | Not recorded (see the report) | Open |
1 High, 2 Low. In the firm’s own words; statuses are the firm’s, from each report.
All of the initial `Devomon` tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.
The audit on Trustblock · Open the reportThe compiler for Solidity 0.8.20 switches the default target EVM version to [Shanghai](https://blog.soliditylang.org/2023/05/10/solidity-0.8.20-release-announcement/#important-note), which includes the new `PUSH0` op code. This op code may not yet be implemented on all L2s, so deployment on these chains will fail. To work around this issue, use an earlier [EVM](https://docs.soliditylang.org/en/v0.8.20/using-the-compiler.html?ref=zaryabs.com#setting-the-evm-version-to-target) [version](https://book.getfoundry.sh/reference/config/solidity-compiler#evm_version)
The audit on Trustblock · Open the reportThe linked statements do not affect the functionality of the codebase and appear to be either remnants of test code or older functionality.
The audit on Trustblock · Open the reportThe Devomon security record · Every Devomon address · This address on the explorer