This document is a security audit report performed by danbogd, where LCX2 has been reviewed.
Сommit hash 1021bf8e087d1c3bd56ddc9f7f117e5d94a727ca.
In total, 4 issues were reported including:
- 0 medium severity issues
- 3 low severity issues
- 1 owner privileges (ability of owner to manipulate contract, may be risky for investors).
- 0 notes.
No critical security issues were found.
Incoming addresses should be checked for an empty value(0x0 address).
Contract owner allow himself to:
- upgrade contract and implement any logic in the new contract. And even if the new contract will be audited, at any time possible to change the address of the new contract again to not audited and insecure.
There are no checks that the beneficiary address can be a contract address.
Example:
The user was able to divest himself of his interest even though the tokens never moved. He didn’t sell the timelocked tokens itself. He sold the future ownership of the tokens. The user is asked by the deployer of the LCX vesting contract for the address where he’d like to receive his tokens after the releaseTime expires in 3 years. User deploys the “Bypasser” contract and gives its address to the deployer of the LCX vesting contract. The Bypasser contract didn’t magically make the timelocked tokens transferable — it made the future ownership of the timelocked tokens transferable.
More details here.
Lack of transaction handling mechanism issue. WARNING! This is a very common issue and it already caused millions of dollars losses for lots of token users! More details here.
Add the following code to the transfer(_to address, ...) function:
require( _to != address(this) );
The review did not show any critical issues, some of low severity issues were found.