Inverse-protocol
SolidProof reviewed Inverse-protocol on 18 Mar 2022: 10 findings, 0 critical; none marked fixed.
No open critical findings
Open the reportOpen Inverse-protocol’s security record
Report stored on IPFS. Content hash bafybeicukm5euy4ufgndx5hgceq4xjp2lhzopgkwvksv4sasjy4jrwsamq
Statuses are the security firm’s own, from this report. Trustblock does not review code.
Findings10
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 | 10 | 0 | 0 |
No acknowledged finding in this report.
Contracts in scope1
| Address | Chain | Source code |
|---|---|---|
| 0xef5230e2dc11e9c8b463df8eca77074d7e636def | Chain: BNB Chain | Source code: Verified source |
Part of Inverse-protocol’s security record
Inverse-protocol
Audits1 audit by 1 firmLast audit Mar 2022, by SolidProof.
Critical findingsNo open critical findingsIn 1 report.
Open Inverse-protocol’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