Sperax audit reports

Arbitrum, Ethereumsperax.ioX

Sperax has 1 public audit report from Quantstamp; dated 11 Dec 2023; no critical findings reported. It also holds 1 incident (latest 3 Feb 2023).

Critical findings
No open critical findings
In 1 report.
Incident
Incident 3 Feb 2023
Source: De.Fi incident database. 1 audit has been published since. See the incident
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 firm15

Statuses are the security firms’ own

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

High
1
Medium
2
Low
12
  • High Acknowledged

    DoS of SPA Oracle Contract

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Medium Acknowledged

    User’s Collateral Could Be Arbitrary Allocated to Undesired Strategies

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Medium Acknowledged

    Users May Lose USDs Yields when Redeeming Collateral

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Low Acknowledged

    Address Aliasing May Affect Cross-Chain Access Control

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Low Acknowledged

    Critical Role Transfer Not Following Two-Step Pattern

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Low Acknowledged

    External Risks that May Affect Protocol Security

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Low Acknowledged

    Fees Are Calibrated Imprecisely

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Low Acknowledged

    Off-by-One Error in USDs Token Balances

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Low Acknowledged

    Ownership Can Be Renounced

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

  • Low Acknowledged

    Potential Fund Losses in Emergency Withdraw of the Stargate Strategy

    Sperax - USDs · Quantstamp · 11 Dec 2023 · Report ↗

All 15 open and acknowledged findings

Incidents1

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

Incident

Incident,

On Feb.

Source: De.Fi incident database.

Audits before it
0.
Audits since
1, the latest dated 11 Dec 2023.

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Sperax - USDsSecurity firm: QuantstampDate: Scope: Repository at commit a4cb9acNone openFindings: 4 high · 3 medium · 21 low
13 fixed · 15 acknowledged
certificate.quantstamp.com ↗

Findings32

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

SeverityOpenAcknowledgedFixed
Critical000
High013
Medium021
Low0129

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.

The repositories and files the reports name

Sperax: questions

Is Sperax audited?

Trustblock holds 1 public audit report for Sperax, dated 11 Dec 2023. The latest is by Quantstamp (“Sperax - USDs”).

Who audited Sperax?

Quantstamp wrote the report Trustblock holds for Sperax.

Are there open findings in Sperax’s audits?

15 findings are still open or acknowledged in the firms’ reports: 1 high, 2 medium, 12 low (all acknowledged). No critical finding is reported. 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="sperax"
></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