Naka Token

QuillAudits24 Jan 20241 address on Polygon (POS)

Audit · firm’s term: audit report

QuillAudits reviewed Naka Token on 24 Jan 2024: 4 findings, 0 critical; all marked fixed.

No open critical findings

Open the report Open Naka Token’s security record

Report hosted on quillaudits.com.

Trustblock does not review code.

Findings4

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

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

LowAn older release of Openzeppelin is being used.Fixed

The latest release of Openzeppelin v5.0.0 or later is recommended. It includes crucial changes such as Ownable2Step.

LowReentrancyGuard is not neededFixed

The Reentrancy Guard is presently unused within the contract, and its necessity is not evident. Consequently, it is recommended to remove the Reentrancy Guard from the codebase to streamline and simplify the contract. This action aligns with best practices and enhances the overall clarity of the code without compromising security.

LowSafeMath is not neededFixed

SafeMath is a library commonly employed to mitigate the risks of underflow and overflow in mathematical operations, particularly in compiler versions preceding 0.8.0. It is important to note that the current contract utilizes compiler version 0.8.23 for compilation. Given this updated compiler version, SafeMath precautions are no longer necessary, as the compiler itself incorporates enhanced safety features.

LowUse SafeERC20 to transfer tokens.Fixed

The 'recoverERC20' function in the smart contract code transfers ERC20 tokens to the owner without checking the return value of the 'transfer' function. According to the ERC20 standard, the 'transfer' function should return a boolean value indicating success or failure. Ignoring this return value can lead to a false assumption that the transfer was successful when it may have failed, which is particularly dangerous in a function designed to recover tokens.