Findings
Issue 01
Type
Severity
Location
Status
Logical Issue
Informational
inGame
✔️ Resolved
Description
The else
statement seems to be redundant.
Recommendation:
Issue 02
Type
Severity
Location
Status
Owner Capabilities
High
inGame
✔️ Resolved
Description
Limit the amount of tokens that can be rewarded in one call to something reasonable, or the owner of the contract / hacker can mint 10% of the total supply in one call.
Recommendation
Consider adding a limit to the amount of tokens the function will mint.
Issue 03
Type
Severity
Location
Status
Best Practice
Low
All
✔️ Resolved
Description
Certain exchanges may require to be excluded from fees but there is no way to do that.
Recommendation
Add an excludeFromFee function.
Issue 04
Type
Severity
Location
Status
Owner Capabilities
High
setTransferFeeRates
✔️ Resolved
Description
The owner of the contract can set the transfer fee to any value they desire. If the owner sets the fee to 100% the token will be untradeable.
Recommendation
Consider adding an upper limit to the set functions.
Last updated