zkNoid Audit
Audit · firm’s term: security review
Extropy reviewed zkNoid (zkNoid Audit) on 9 Sep 2024: 9 findings, 0 critical; 6 marked fixed, 3 open.
No open critical findings
Open the reportOpen zkNoid’s security record
Report stored on IPFS. Content hash bafybeiejszikgmqd6g6j6fvh63q5ialfaiobwvlx5v3pcopwm4bdkn7uqy
Trustblock does not review code.
Findings9
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 1 |
| Medium | 1 | 0 | 3 |
| Low | 2 | 0 | 2 |
MediumCurrent design heavily relies on a centralized backendOpen
The report gives no description here.
LowNon standard implementationOpen
Non standard reimplementation of ‘MerkleMap‘ and ‘MerkleMapWitness‘
LowPossible Hash CollisionOpen
Possible hash collision may causes different tickets to have the same ‘ticketId‘
Contracts in scope1
| Address | Chain |
|---|---|
| B62qmLSzDY2uF8yD6Dqy5bdjff2gSqJuwypekAeRiQVCZRsRoq4dV4o | Chain: Mina protocol |
Part of zkNoid’s security record
zkNoidAudits1 audit by 1 firmLast audit Sep 2024, by Extropy.
Critical findingsNo open critical findingsIn 1 report.
Open zkNoid’s security recordSecurity firm
Extropy9 projects reviewed · 12 reports · latest Mar 2025
See Extropy’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