SpaceFi 2.0 audit reports

SpaceFi 2.0 has 3 public audit reports from QuillAudits; the latest is QuillAudits, 19 Jan 2023; no critical findings reported.

Critical findings
No open critical findings
Across 3 reports.
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 firm7

Statuses are the security firms’ own

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

High
3
Medium
1
Low
3
  • High Open

    Reentrancy

    SpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023 · Report ↗

  • High Open

    Unprotected Initialize

    SpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023 · Report ↗

  • High Open

    Upgradeable Best Practises

    SpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023 · Report ↗

  • Medium Open

    1. Centralization Risks / Overpowered Ownership

    SpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023 · Report ↗

  • Low Open

    1. Uninitialized and unused logic

    SpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023 · Report ↗

  • Low Open

    Untitled finding

    Spacefi - new · QuillAudits · 22 Sep 2022 · Report ↗

  • Low Open

    Untitled finding

    Spacefi - new · QuillAudits · 22 Sep 2022 · Report ↗

Audits3

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
SpaceFi -xEVMOSTokenSecurity firm: QuillAuditsDate: Scope: Files listedNone openFindings: 3 high · 1 medium · 1 low
5 open
quillaudits.com ↗
Spacefi - newSecurity firm: QuillAuditsDate: Scope: Files listedNone openFindings: 2 low
2 open
quillaudits.com ↗
SpaceFiSecurity firm: QuillAuditsDate: Scope: Files listedNone openFindings: 1 medium · 1 low
2 fixed
quillaudits.com ↗

Findings12

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

SeverityOpenAcknowledgedFixed
Critical000
High300
Medium101
Low301
HighReentrancySpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023Open

Line 415function finalizeRedeem(uint256 redeemIndex) external validateRedeem(msg.sender, redeemIndex) { Above function does not follow checks effects interaction patterns where an external call is made in internal function Line 444 _finalizeRedeem() and an attacker contract can reenter the finalizeRedeem function again to get same EvmosAmount on the same RedeemInfo in userRedeems that has not yet been deleted which only happens in Line 436 _deleteRedeemEntry(redeemIndex);

Open the report
HighUnprotected InitializeSpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023Open

Without clear documentation if the contracts make use of Hardhat plugins which ensure the initialize function is called when contracts Proxy deployed, it is possible to deploy contracts and forget to call initialize or it can be front run by an attacker taking over the contracts.

Open the report
HighUpgradeable Best PractisesSpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023Open

It is recommended for upgradeable contracts to not reinvent the wheel and follow best practices like making use of OpenZeppelin ERC20Upgradeable contracts, UUPS upgradeable pattern plus Hardhat Upgradeable plugins when creating and deploying upgradeable contracts. This safeguards from forgetting crucial upgrade logic, running initializers multiple times, not miss ERC20 compatibility,  not introducing errors or bugs by rewriting contracts, ensuring efficient safer contracts, not forgetting public mint functions(in cases where needed- in this case not needed), more compact and easier to reason, maintainability, modularity, and it follows best practises.

Open the report
Medium1. Centralization Risks / Overpowered OwnershipSpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023Open

Without clear documentation if the Ownable contract will make use of decentralised control such as MultiSig. The owner has control to update whitelists, update redeem settings, upgrade contracts. Any compromise to the Owner account may allow the hacker to take advantage of this.

Open the report
Low1. Uninitialized and unused logicSpaceFi -xEVMOSToken · QuillAudits · 19 Jan 2023Open

State variable Line 56 mapping(address => uint256) private _farmStakingBalances; is never initialised and or updated in the contracts or used in any other functionality. Function Line 155 function farmStakingBalancOf(address) will always return 0 for all addresses.

Open the report
LowUntitled findingSpacefi - new · QuillAudits · 22 Sep 2022Open

The report gives no description here.

Open the report
LowUntitled findingSpacefi - new · QuillAudits · 22 Sep 2022Open

The report gives no description here.

Open the report

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

SpaceFi 2.0: questions

Is SpaceFi 2.0 audited?

Trustblock holds 3 public audit reports for SpaceFi 2.0, dated 27 May 2022 to 19 Jan 2023. The latest is by QuillAudits (“SpaceFi -xEVMOSToken”).

Who audited SpaceFi 2.0?

QuillAudits wrote the 3 reports Trustblock holds for SpaceFi 2.0.

Are there open findings in SpaceFi 2.0’s audits?

7 findings are still open or acknowledged in the firms’ reports: 3 high, 1 medium, 3 low (all open). 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="spacefi-20"
></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