Naka Token security record

Polygon (POS)

As of 3 Nov 2026, Naka Token has 1 audit report on Trustblock, by QuillAudits, dated 24 Jan 2024. That report lists no open critical findings. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.

Audits1

Newest first

AuditSecurity firmDateScopeCritical findingsReport
Naka Token

Audit

Security firm: QuillAuditsDate: Scope: 1 address on Polygon (POS)No open critical findingsOpen · quillaudits.com

Findings4

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low004
LowAn older release of Openzeppelin is being used.Naka Token · QuillAudits · 24 Jan 2024Fixed

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

Open the report
LowReentrancyGuard is not neededNaka Token · QuillAudits · 24 Jan 2024Fixed

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.

Open the report
LowSafeMath is not neededNaka Token · QuillAudits · 24 Jan 2024Fixed

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.

Open the report
LowUse SafeERC20 to transfer tokens.Naka Token · QuillAudits · 24 Jan 2024Fixed

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.

Open the report

Contracts1

AddressChainSource code
Chain: Polygon (POS)Source code: Verified source

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
	<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
	<div
		data-tb-project-widget
		data-tb-project-slug="naka-token"
	></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us