NUTS Finance audit reports

NUTS Finance has 2 public audit reports from MixBytes; the latest is MixBytes, 8 Sep 2025; 2 critical findings, all marked fixed by the firms.

Critical findings
No open critical findings
Across the 2 reports, 2 critical findings were reported. Each is marked fixed by the firm that reported it. See the findings
Open the latest report
Your label, live
Get the label for your site

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

Open findings across every firm11

Statuses are the security firms’ own

11 findings are still open or acknowledged in the firms’ reports: 1 high, 1 medium, 9 low (all acknowledged).

High
1
Medium
1
Low
9
  • High Acknowledged

    Flawed Precision and Scaling Logic in price()

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Medium Acknowledged

    Centralization Risks in Emergency Scenarios

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    decimals() Can Be a Constant Value

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    Fee-On-Transfer Tokens Not Supported

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    Inconsistent Share Allocation Due to Exchange Rate Fluctuations Within Margin

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    Lack of spa and wlp Address Validation in Zap Contract

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    Missing Zero‐Address Check for Every Feed Entry

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    Rounding‐Error Amplification When Chaining Inverted Price Feeds

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    Unbounded Fee Parameters

    NUTS Finance · MixBytes · 8 Sep 2025 · Report ↗

  • Low Acknowledged

    Missing EIP-165 Interface Compliance Checks

    NUTS Finance · MixBytes · 4 Sep 2025 · Report ↗

All 11 open and acknowledged findings

Audits2

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
NUTS FinanceSecurity firm: MixBytesDate: Scope: Not recorded; see the report1 critical finding, fixedFindings: 1 critical · 4 high · 7 medium · 22 low
25 fixed · 9 acknowledged
GitHub ↗
NUTS FinanceSecurity firm: MixBytesDate: Scope: Not recorded; see the report1 critical finding, fixedFindings: 1 critical · 1 high · 3 medium · 12 low
15 fixed · 2 acknowledged
GitHub ↗

Findings51

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

SeverityOpenAcknowledgedFixed
Critical002
High014
Medium019
Low0925

No open finding in these reports.

Contracts

No deployed address is recorded for these audits.

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

NUTS Finance: questions

Is NUTS Finance audited?

Trustblock holds 2 public audit reports for NUTS Finance, dated 4 Sep 2025 to 8 Sep 2025. The latest is by MixBytes (“NUTS Finance”).

Who audited NUTS Finance?

MixBytes wrote the 2 reports Trustblock holds for NUTS Finance.

Are there open findings in NUTS Finance’s audits?

11 findings are still open or acknowledged in the firms’ reports: 1 high, 1 medium, 9 low (all acknowledged). Of 2 critical findings: all marked fixed by the firms. Statuses are the security firms’ own.

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="nuts-finance"
></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