0xe846dd34dc07ab517e78f5e58edae79d80222fd0
As of 21 Nov 2026, Trustblock’s record holds 0xe846dd34dc07ab517e78f5e58edae79d80222fd0 on BNB Chain as a contract of MEFLEX. 1 audit report on Trustblock lists this address: CertiK, 18 Mar 2024. 2 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 |
|---|---|---|---|---|
| Meflex Token | CertiK | Not recorded (see the report) | Open |
2 High. In the firm’s own words; statuses are the firm’s, from each report.
In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and transfer the ownership to one of his EoAs or renounce the ownership. 
The audit on Trustblock · Open the reportAll of the `MEF` 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 MEFLEX security record · Every MEFLEX address · This address on the explorer