Nova security record

Ethereumnova.win

As of 14 Oct 2026, Nova has 2 audit reports by 2 security firms on Trustblock; the latest is by Hacken, dated 20 Feb 2025. Those reports list no open critical findings. It also holds 1 incident (latest 18 Apr 2021).

Critical findings
No open critical findings
Across 2 reports.
Incident
Incident 18 Apr 2021
Source: De.Fi incident database. 2 audits have been published since. See the incident
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Statuses are the security firms’ own. Trustblock does not review code.

Audits2

Newest first

AuditSecurity firmDateScopeCritical findingsReport
Astra Nova / Rvv-TokenSecurity firm: HackenDate: Scope: Files named in the reportNo open critical findingsOpen · audits.hacken.io
Astra NovaSecurity firm: QuillAuditsDate: Scope: Files named in the reportNo open critical findingsOpen · quillaudits.com

Findings5

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low005
LowSolidity Version 0.8.28 Might Not Work On All ChainsAstra Nova / Rvv-Token · Hacken · 20 Feb 2025Fixed

The report gives no description here.

Open the report
LowUnclear naming for burn() function.Astra Nova / Rvv-Token · Hacken · 20 Feb 2025Fixed

The report gives no description here.

Open the report
LowUse Custom Errors Instead of Long Revert StringsAstra Nova / Rvv-Token · Hacken · 20 Feb 2025Fixed

The report gives no description here.

Open the report
LowAvoid using floating pragmaAstra Nova · QuillAudits · 18 Jun 2024Fixed

Floating pragma should only be used when a contract is intended for consumption by other developers.Locking the pragma helps ensure that contracts are not accidentally deployed using, for example, the latest compiler, which may have higher risks of undiscovered bugs.

Open the report
LowMissing gap variable for upgradeable contractsAstra Nova · QuillAudits · 18 Jun 2024Fixed

For upgradeable contracts, there must be a storage gap to “allow developers to freely add new state variables in the future without compromising the storage compatibility with existing deployments” (quote OpenZeppelin). Otherwise it may be very difficult to write new implementation code. Without a storage gap, the variable in the child contract might be overwritten by the upgraded base contract if new variables are added to the base contract. This could have unintended and very serious consequences to the child contracts, potentially causing loss of user funds or causing the contract to malfunction completely.Refer here: https://docs.openzeppelin.com/upgrades-plugins/1.x/writing-upgradeable

Open the report

Incidents1

Attached through a shared contract address. Our incident data ends in Oct 2026.

Incident

Incident,

The contract owner could disable the transfer function, which restricted users in selling their tokens.

Source: De.Fi incident database.

Audits before it
0.
Audits since
2, the latest dated 20 Feb 2025.

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

The repositories and files the reports name

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="nova"
></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