Ezzy Audit

CertiKFiles named in the report

CertiK reviewed EZZY Game (Ezzy Audit) on 21 Apr 2023: 2 findings, 0 critical; none marked fixed.

No open critical findings
Open the reportOpen EZZY Game’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
High200
Medium000
Low000
HighInitial Token DistributionOpen

All the initially minted EZZY tokens (total `2000000000000000000000000` tokens) are sent to the deployer during the contract deployment. This could lead to possible centralization related risks, such as: - The deployer can distribute the tokens without obtaining the consensus of the community. - If the deployer's private key is compromised, the attacker can obtain a great number of tokens and sell them for profit.

HighTokens Can Be Minted by OwnerOpen

The owner has the privilege to mint tokens to his account. If the private key of the owner is compromised, the attacker can mint tokens, sell the tokens, and cause a severe impact on the project. ```solidity=165 function mint(uint256 amount) external onlyOwner() returns (bool) { _mint(_msgSender(), amount); return true; } ```

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 (5)

  • utils/Context.sol
  • utils/SafeMath.sol
  • utils/Ownable.sol
  • BEP20Token.sol
  • utils/IBEP20.sol

Part of EZZY Game’s security record

EZZY Game
Audits2 audits by 1 firmLast audit Jul 2023, by CertiK.
Critical findingsNo open critical findingsAcross 2 reports.
Open EZZY Game’s security record

Security firm

CertiK

1,045 projects reviewed · 1,376 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