Ethernity Cloud

CertiK2 Nov 2023Files named in the report

Audit

CertiK reviewed Ethernity CLOUD on 2 Nov 2023: 6 findings, 0 critical; 1 marked fixed, 2 acknowledged, 3 open.

No open critical findings

Open the report Open Ethernity CLOUD’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings6

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	0	2	1
Medium	0	0	0
Low	3	0	0

LowInefficient Memory ParameterOpen

One or more parameters with `memory` data location are never modified in their functions and those functions are never called internally within the contract. Thus, their data location can be changed to `calldata` to avoid the gas consumption copying from calldata to memory. ```solidity=16 function mint( ``` `mint` has memory location parameters: `mintId`.

LowToo Many DigitsOpen

Literals with many digits are difficult to read and review. ```solidity=15 uint256 private immutable _initialCap = 1000000000 * (10**decimals()); // 1 billion ECLD (Wei) ``` --- ```solidity=16 uint256 private immutable _initialBalance = 105000000 * (10**decimals()); // 1 million ECLD (Wei) ```

LowUnnecessary Operation In ConstructorOpen

Since the value `_initialBalance` has been set to zero, the `constructor` of the contract `EthernityCloudERC20` performs an unnecessary minting operation. In particular, it will try to mint zero tokens to the `msg.sender`: ```solidity _mint(msg.sender, _initialBalance); ```