SnarkLaunch contract 0x3eb6…58ff on zkSync

0x3eb6b6b344a7af4bab64210ea64f19d7c2cc58ff

As of 21 Nov 2026, Trustblock’s record holds 0x3eb6b6b344a7af4bab64210ea64f19d7c2cc58ff on zkSync as a contract of SnarkLaunch. 1 audit report on Trustblock lists this address: CertiK, 17 Apr 2023. 3 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 zkSync.

AuditSecurity firmDateCommit named in the reportReport
Snark LaunchCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports3

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

HighInitial Token DistributionSnark Launch · CertiKOpen

All **Snark Launch** tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute **Snark Launch** tokens without the consensus of the community.

The audit on Trustblock · Open the report
LowIt is better to use a proxy patternSnark Launch · CertiKOpen

It's recommended to use the proxy pattern by the zkSync. https://era.zksync.io/docs/dev/building-on-zksync/contracts/differences-with-ethereum.html#recommendations

The audit on Trustblock · Open the report
LowProper usage of “pure” and “view”Snark Launch · CertiKOpen

Function state mutability can be restricted to pure, functions can be declared pure in which case they promise not to read from or modify the state.

The audit on Trustblock · Open the report

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