CRI3X
SolidProof reviewed Cri3x on 22 Feb 2023: 5 findings, 0 critical; none marked fixed.
No open critical findings
Open the reportOpen Cri3x’s security record
Report stored on IPFS. Content hash QmSyY5JJkC3hqVnn5nQnJw7a6Dbbg9qLs6U9VhYQUN7omp
Trustblock does not review code.
Findings5
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 | 5 | 0 | 0 |
Low#1: Uninitialised State VariablesOpen
The report gives no description here.
Low#1: Unused return valuesOpen
The report gives no description here.
Low#2: Missing Zero Address Validation (missing-zero-check)Open
The report gives no description here.
Low#2: NatSpec documentation missingOpen
The report gives no description here.
Low#3: Owner can drain tokensOpen
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 (2)
- contracts/Cri3X.sol
- v1.1
Part of Cri3x’s security record
Cri3x
Audits2 audits by 1 firmLast audit Mar 2023, by SolidProof.
Critical findingsNo open critical findingsAcross 2 reports.
Open Cri3x’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