Skip to content

Instantly share code, notes, and snippets.

@yuriy77k

yuriy77k/ETH_LuckyStrike_v4_report.md Secret

Forked from MrCrambo/ETH_LuckyStrike_v4_report.md
Created May 30, 2019 07:36
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save yuriy77k/988cf0e4b5da6393442374944deb08ae to your computer and use it in GitHub Desktop.
Save yuriy77k/988cf0e4b5da6393442374944deb08ae to your computer and use it in GitHub Desktop.
Download ZIP
Raw
ETH_LuckyStrike_v4_report.md

Summary

This is the report from a security audit performed on LuckyStrike v4 by MrCrambo.

The audit focused primarily on the security of LuckyStrike v4 smart contracts.

In scope

  1. https://ropsten.etherscan.io/address/0xbce45fee20ebfa7ee8c0e6ee9755753883a48b05#code
  2. https://ropsten.etherscan.io/address/0x830991dc0bd8250def572bacd01f4c4cacb1fdb7#contracts

Findings

In total, 2 issues were reported including:

  • 0 high severity issues.

  • 0 medium severity issues.

  • 1 owner privilegies issues.

  • 1 low severity issues.

Security issues

1. Possibility of minting more than hardCap

Severity: low

Description

Function mint allows owner to mint more tokens than hardCap. Line 353.

2. Owner privilegies

Severity: owner privilegies

Description

adjustAllocation function allows the owner to reset the rates of the different jackpots and income rate.

Conclusion

Smart contract contains low severity issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment