EclipseFi security record
As of 29 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 |
MediumExternal dependency on incentive distribution in lp_stakingEclipseFi · Resonance Security · 2 Oct 2024Open
The lp_staking contract relies on external sources to send incentives for distribution to stakers, as it lacks the ability to mint rewards internally. This creates a vulnerability where stakers may not receive expected rewards if the external sources fail or are compromised. An attacker or misconfigured system could disrupt reward distribution, leading to loss of user trust and participation in the staking mechanism.
Open the reportMediumExternal Dependency on Incentive Distribution in single_sided_staking contractEclipseFi · Resonance Security · 2 Oct 2024Open
The single_sided_staking contract relies on external sources to send incentives for distribution to stakers, as it lacks the ability to mint rewards internally. This creates a vulnerability where stakers may not receive expected rewards if the external sources fail or are compromised. An attacker or misconfigured system could disrupt reward distribution, leading to loss of user trust and participation in the staking mechanism.
Open the reportLowLack of parameter validation in try_update_date_config functionEclipseFi · Resonance Security · 2 Oct 2024Open
The try_update_date_config function in the voter contract lacks proper validation for critical parameters such as genesis_epoch_start_date, epoch_length, and vote_delay. While the function allows updating these values, it does not perform any validation checks to ensure that the provided inputs are within acceptable ranges or follow a logical sequence (e.g., future dates, minimum/maximum values for epoch length and vote delay).
Open the reportLowDuplicated functionalityEclipse Fi · Zokyo · 14 Dec 2023Open
The report gives no description here.
Open the reportLowDuplicated functionalityEclipse Fi · Zokyo · 14 Dec 2023Open
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