Lucky Strike v3 #219
Lucky Strike, based fully in Ethereum smart-contract, is bringing the core philosophy of blockchain to the gambling industry – enhancing it with an ICO model we’re calling ‘Bet & Own.’
You can write about any issues directly in the comments.
Changes after previous audit:
Number of lines:
1618 * 0.5 (reaudit coeficient) = 809
1 similar comment
Lucky Strike v3 Security Audit Report
2. In scope
In total, 3 issues were reported including:
No critical security issues were found.
3.1. It is possible to use Ahead of The Curve strategy
Formula of the random calculation is:
bytes32 seed = keccak256( block.blockhash(lastInstantGameBlockNumber[player]) ); uint256 randomNumber = uint256(seed) % ticketsInTheInstantGame;
The result of the player's fight with the King of the hill is known immediately after the player has placed a bet. But the result will be applied only after calling the
There should not be a gap between reliable information that someone won between the fact of this. A good solution would be to play all the instant games in the first block after the any bet. Even if there were several bets in one block, they all need to be played at the first next appeal to the contract.
3.2. Possibility of minting more than hardCap
You should check
3.3. Owner Privileges
Severity: owner privileges
The audited smart contract must not be deployed. Medium severity issue must be fixed prior to the usage of this contract.
5. Revealing audit reports