MEMEVENGERS - Audit

CertiKFiles named in the report

CertiK reviewed MEMEVENGERS (MEMEVENGERS - Audit) on 28 Jun 2023: 2 findings, 0 critical; all acknowledged, none fixed.

No open critical findings
Open the reportOpen MEMEVENGERS’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings2

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High010
Medium000
Low010
HighInitial Token DistributionAcknowledged

All of the initially minted `MemevengersToken` tokens are sent to the contract deployer address. 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 this address may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project. ```solidity=8 constructor( string memory name_, string memory symbol_, uint256 initialSupply ) ERC20(name_, symbol_) { _mint(msg.sender, initialSupply); } ``` As of Jun 21, 2023, the project was deployed at the address [0xddf688e96cb2531a69bf6347c02f069266c1aa81](https://etherscan.io/token/0xddf688e96cb2531a69bf6347c02f069266c1aa81#code). Based on the on-chain investigation, here are the major holders. - 0x3CC936b795A188F0e246cBB2D74C5Bd190aeCF18 (Mexc.com 3): 10.0749% - 0x15928c01d1BF49638986a58A773A84d52990823b: 8.6596% - 0x855FA1B0c27FEfC055c1880C5A5969Ee731e9690 (Uniswap V3: MMVG): 6.8910% - 0x75e89d5979E4f6Fba9F97c104c2F0AFB3F1dcB88 (Mexc.com): 1.5613% Additionally, the token of [0x15928c01d1BF49638986a58A773A84d52990823b](https://etherscan.io/token/0xddf688e96cb2531a69bf6347c02f069266c1aa81?a=0x15928c01d1bf49638986a58a773a84d52990823b) were received from [0x3116D0D87892Bc41D06431A46EA1210fd94557FB](https://etherscan.io/token/0xddf688e96cb2531a69bf6347c02f069266c1aa81?a=0x3116d0d87892bc41d06431a46ea1210fd94557fb), which received the initially distributed tokens.

LowUnlocked Compiler VersionAcknowledged

The contracts cited have an unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to differing compiler version numbers. This can lead to ambiguity when debugging, as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (1)

  • contracts/MEMEVENGERS.sol

Part of MEMEVENGERS’s security record

MEMEVENGERS
Audits1 audit by 1 firmLast audit Jun 2023, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open MEMEVENGERS’s security record

Security firm

CertiK

1,044 projects reviewed · 1,375 reports · latest May 2025

See CertiK’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us