Spool Arbitrum security review
Hexens reviewed Spool (Spool Arbitrum security review) on 26 Apr 2024: 7 findings, 0 critical; 3 marked fixed, 4 acknowledged.
No open critical findings
Findings7
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 1 |
| Medium | 0 | 2 | 2 |
| Low | 0 | 2 | 0 |
MediumLack of slippage protection in _compoundAcknowledged
The report gives no description here.
MediumUsage of hardcoded lockDuration may lead to loss of extra rewardsAcknowledged
The report gives no description here.
Low_compound doesn't use return value of _getProtocolRewardsInternalAcknowledged
The report gives no description here.
LowUsing block.timestamp as deadlineAcknowledged
The report gives no description here.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Part of Spool’s security record
SpoolAudits10 audits by 2 firmsLast audit Sep 2024, by Hexens.
Critical findingsNo open critical findingsAcross the 10 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open Spool’s security recordSecurity firm
Hexens32 projects reviewed · 75 reports · latest Jul 2026
See Hexens’s auditsSomething 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