zkNoid contract B62qmL…dV4o on Mina protocol

B62qmLSzDY2uF8yD6Dqy5bdjff2gSqJuwypekAeRiQVCZRsRoq4dV4o

As of 21 Nov 2026, Trustblock’s record holds B62qmLSzDY2uF8yD6Dqy5bdjff2gSqJuwypekAeRiQVCZRsRoq4dV4o on Mina protocol as a contract of zkNoid. 1 audit report on Trustblock lists this address: Extropy, 11 Oct 2024. 4 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on Mina protocol.

AuditSecurity firmDateCommit named in the reportReport
zkNoid AuditExtropyNot recorded (see the report)Open

Open and acknowledged findings in these reports4

1 High, 2 Medium, 1 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighNo zero check on amounts of tickets boughtzkNoid Audit · ExtropyOpen

No zero check on amounts of tickets bought

The audit on Trustblock · Open the report
Medium‘seed‘ input lengthzkNoid Audit · ExtropyOpen

‘generateNumbersSeed()‘ output can be manipulated by ‘seed‘ input length

The audit on Trustblock · Open the report
MediumCurrent design heavily relies on a centralized backendzkNoid Audit · ExtropyAcknowledged

The report gives no description here.

The audit on Trustblock · Open the report
LowPossible Hash CollisionzkNoid Audit · ExtropyOpen

Possible hash collision may causes different tickets to have the same ‘ticketId‘

The audit on Trustblock · Open the report

The zkNoid security record · Every zkNoid address · This address on the explorer