Opsec Staking
SolidProof reviewed OpSec (Opsec Staking) on 1 May 2024: 3 findings, 0 critical; 1 marked fixed, 2 acknowledged.
No open critical findings
Open the reportOpen OpSec’s security record
Report stored on IPFS. Content hash Qmdn98PtYqXjmoLQFGJYuF45PHwNQMBsbCZapntJfTmcCs
Trustblock does not review code.
Findings3
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 1 |
| Medium | 0 | 1 | 0 |
| Low | 0 | 1 | 0 |
MediumOwner can lock user fundsAcknowledged
The report gives no description here.
LowFloating PragmaAcknowledged
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.
Repository and files the report names (1)
- https://github.com/opseccloud/staking/blob/main/contracts/OpsecStaking.sol/contracts/OpsecStaking.sol at commit a55d4a5
Part of OpSec’s security record
OpSecAudits2 audits by 2 firmsLast audit Jul 2024, by Hacken.
Critical findingsNo open critical findingsAcross 2 reports.
Open OpSec’s security recordSecurity firm
SolidProof1,127 projects reviewed · 1,478 reports · latest Feb 2025
See SolidProof’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