EDUM - Audit

CertiK17 Mar 2023Files named in the report

Audit

CertiK reviewed EDUM (EDUM - Audit) on 17 Mar 2023: 13 findings, 0 critical; 2 marked fixed, 11 open.

No open critical findings

Open the report Open EDUM’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings13

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

Severity	Open	Fixed
Critical	0	0
High	0	0
Medium	0	1
Low	11	1

MediumFunds Can Be Accidentally LockedFixed

On line 286 the comment line below can cause unintended bugs if followed: ```solidity * @param _releaseTime The timestamp to unlock token. ``` If the future timestamp is input into `transferPreTimelock()`, then the timelock will accidentally be put far into the future due to the line below: ```solidity releaseTime = lockStates[_addr].lockInfo[ii].releaseTime + listingDate; ``` This will add the timestamp of the `listingDate` and the `releaseTime` which will be unintended. This will also increase `minReleaseTime` to the same value which will fail in the future unless a new timelock is sent to reset `minReleaseTime` ```solidity if (lockStates[_addr].minReleaseTime > block.timestamp) return; ```

LowLeft Over Test CodeFixed

The following functions are leftover from testing and should be removed before the token is deployed: - `getLockedCount()` - `dummy()`