EclipseFi security record
As of 30 Oct 2026, EclipseFi has 2 audit reports by 2 security firms on Trustblock; the latest is by Resonance Security, dated 2 Oct 2024. Those reports list no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits2
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| EclipseFi | Security firm: Resonance Security | Date: | Scope: Repository, no commit named | No open critical findings | Open · IPFS |
| Eclipse Fi | Security firm: Zokyo | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · IPFS |
Findings13
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 1 |
| Medium | 2 | 0 | 0 |
| Low | 3 | 0 | 7 |
HighDepositPrivateSale could be executed in a Public Sale periodEclipse Fi · Zokyo · 14 Dec 2023Fixed
The report gives no description here.
Open the reportLowLack of Two-Step Admin Ownership Accept in lp_staking ContractEclipseFi · Resonance Security · 2 Oct 2024Fixed
The lp_staking contract lacks a two-step ownership transfer acceptance mechanism. Currently, ownership of the contract can be transferred in a single transaction without requiring acceptance or verification from the new owner. This practice introduces operational risks and potential vulnerabilities.
Open the reportLowLack of Two-Step Admin Ownership Accept in single_side_staking contractEclipseFi · Resonance Security · 2 Oct 2024Fixed
The single_side_staking contract lacks a two-step ownership transfer acceptance mechanism. Currently, ownership of the contract can be transferred in a single transaction without requiring acceptance or verification from the new owner. This practice introduces operational risks and potential vulnerabilities.
Open the reportLowPresence of unused commented-out code in the codebaseEclipseFi · Resonance Security · 2 Oct 2024Fixed
The codebase contains sections of commented-out code, which are not actively contributing to the functionality of the system. These comments include blocks of code that were likely used during development or testing but were never removed from the final version. While not executed, this code still remains within the repository, serving no functional purpose.
Open the reportLowUnused importEclipse Fi · Zokyo · 14 Dec 2023Fixed
The report gives no description here.
Open the reportLowUnused importEclipse Fi · Zokyo · 14 Dec 2023Fixed
The report gives no description here.
Open the reportLowUnused variableEclipse Fi · Zokyo · 14 Dec 2023Fixed
The report gives no description here.
Open the reportLowUse of deprecated functionEclipse Fi · Zokyo · 14 Dec 2023Fixed
The report gives no description here.
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
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
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.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="eclipse-fi"></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