OpSec / OpSec-Contracts
Hacken reviewed OpSec (OpSec-Contracts) on 26 Jul 2024: 6 findings, 0 critical; all marked fixed.
No open critical findings
Open the reportOpen OpSec’s security record
Report hosted on hacken.io.
Trustblock does not review code.
Findings6
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 0 | 6 |
LowBot-Flagged Addresses Can Still Receive TokensFixed
The report gives no description here.
LowGas Inefficiency Due to Missing Usage of Solidity Custom ErrorsFixed
The report gives no description here.
LowInefficient Storage Types for launchBlock and launchTime in OpSecToken ContractFixed
The report gives no description here.
LowNon-descriptive _owner Argument May Cause MisunderstandingsFixed
The report gives no description here.
LowRedundant Constant Variable in OpSecToken Contract Increase Deployment CostFixed
The report gives no description here.
LowUncontrolled Blacklisting Mechanism in OpSecToken By Contract OwnerFixed
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)
- contracts/OpSecToken.sol
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
Hacken343 projects reviewed · 476 reports · latest Sep 2026
See Hacken’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