Voyager Token

Quantstamp12 Feb 2021Files named in the report

Quantstamp reviewed Voyager (Voyager Token) on 12 Feb 2021: 10 findings, 0 critical; 6 marked fixed, 2 acknowledged, 2 open.

No open critical findings

Open the report Open Voyager’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings10

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

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

LowAllowance Double-Spend ExploitAcknowledged

As it presently is constructed, the contract is vulnerable to the [allowance double-spend exploit](https://github.com/OpenZeppelin/openzeppelin-solidity/blob/b4f87bb8fc25fb07f73099701e39e167a3d36465/contracts/token/ERC20/ERC20.sol#L71-L78), as with other ERC20 tokens.

LowGas Usage / `for` Loop ConcernsAcknowledged

Gas usage is a main concern for smart contract developers and users, since high gas costs may prevent users from wanting to use the smart contract. Even worse, some gas usage issues may prevent the contract from providing services entirely. For example, if a `for` loop requires too much gas to exit, then it may prevent the contract from functioning correctly entirely. <br><br> The `StakeToken.init` function contains a loop which is bounded by user provided input and hence it could run into an out of gas error if the length of the `minterAddresses` array was long enough.