Incident,
The Hedgey Finance-related contract was drained of approximately 2 million USD.
Source: De.Fi incident database.
- Audits before it
- 1.
- Audits since
- 4, the latest dated 12 Nov 2024.
As of 19 Nov 2026, Hedgey has 5 audit reports by 2 security firms on Trustblock; the latest is by Resonance Security, dated 12 Nov 2024. Those reports list no open critical findings. It also holds 1 incident (latest 18 Apr 2024).
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Newest first
| Report | Security firm | Date | Scope | Critical findings | Source |
|---|---|---|---|---|---|
| Hedgey Finance Delegated Claims Smart Contract | Security firm: Resonance Security | Date: | Scope: —Not recorded; see the report | None open | GitHub ↗ |
| Hedgey Finance | Security firm: Resonance Security | Date: | Scope: 94 addresses on 13 chains | None open | IPFS ↗ |
| Lockup And Delegated Claims Smart Contracts | Security firm: Resonance Security | Date: | Scope: —Not recorded; see the report | None open | GitHub ↗ |
| Hedgey Finance | Security firm: Resonance Security | Date: | Scope: 94 addresses on 13 chains | None open | IPFS ↗ |
| Hedgey Token Lockup and Vesting Plans | Security firm: Consensys | Date: | Scope: Files listed | None open | diligence.security ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 1 | 8 | 2 |
| Low | 3 | 12 | 8 |
Marked Info or Informational by the firms. Not counted as findings.
The report gives no description here.
Open the reportThe report gives no description here.
Open the reportWhen it is not possible for counters to overflow, as is the case when used in for and while-loops, they should be unchecked. The unchecked keyword is new in solidity version 0.8.0, so this only applies to that version or higher, which these instances are. This saves 30-40 gas per loop.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe functions planBalanceOf() and planEnd() do not validate the variable planId against the Zero Value, allowing for incorrect information to be presented by the protocol. Even though a planId of 0 would most likely be invalid, the protocol can still confirm it exists even when it does not. Also it allows for divisions by 0 to occur.
Open the reportIt was observed that throughout the protocol there are multiple instances of redundant code on several accounts:Duplicated functions, e.g planBalanceOf() and planEnd();Similar functions with slight differences do not reuse code, e.g. createUnlockedCampaign() and createLockedCampaign();Similar contracts with slight differences do not use inheritance, e.g. TokenLockupPlans, VotingTokenLockupPlans, TokenVestingPlans and VotingTokenVestingPlans;These design patterns increase code complexity and do not maximize transaction gas and storage efficiency on the blockchain.
Open the reportThe function batchLockingPlans() performs the same Zero Address validation on the variable token already provided by other functions such as transferTokens(), safeIncreaseAllowance(), and createPlan().
Open the reportThe function _claimUnlockedTokens() performs the same validation twice on the same variable campaign.tokenLockup as the functions who call it. The first time always occurs within if conditions, and the second time occurs on _claimUnlockedTokens().
Open the reportThe function validateEnd() defines an output bool variable valid that identifies whether the execution of this function was successful. The usage of this variable is unnecessary since it is always set to true or the entire transaction reverts through the require statements.
Open the reportThe report gives no description here.
Open the reportAccording to the Solidity Style Guide, non-external functions and variable names should begin with an underscore.
Open the reportThe report gives no description here.
Open the reportIndex in for-loops are initialized to 0, which is not necessary.
Open the reportAttached through a shared contract address. Our incident data ends in Nov 2026.
The Hedgey Finance-related contract was drained of approximately 2 million USD.
Source: De.Fi incident database.
The reports name a repository or files. Open a report to see its scope.
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.
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.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="hedgey-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