Holo Token smart contract security audit report performed by Callisto Security Audit Department
In total, 3 issues were reported including:
-
2 low severity issues.
-
1 owner privileges (the ability of an owner to manipulate contract, may be risky for investors).
No critical security issues were found.
-
It is possible to double withdrawal attack. 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) );
There are no zero address checking in functions setMinter
at line 239, setDestroyer
at line 269 and mint
at line 243.
Owner can mint any amount of tokens and for a long period of time, because he can not finish minting and can set himself as minter.
The audited smart contract can be deployed. Only low severity issues were found during the audit.
https://gist.github.com/yuriy77k/c6a8d409a858f6155780ea7f4addd097
https://gist.github.com/yuriy77k/dcea1e26ba3e6e73e5e51a77e5d241d3
https://gist.github.com/yuriy77k/4afef9710e08a8a9030e58c8590019b6