Zolana is an experimental devnet. No independent security audit or cryptographic review has been completed for the protocol, the validator modifications, the wallets or the operator tooling. Only valueless devnet test coins are at stake; they are distinct from the ZOL token issued on Solana.
Report a vulnerability
Send reports to security@zolana.com.
Please do not open a public GitHub issue for a vulnerability, and do not include secrets such as recovery files, passwords or invitation codes in a report.
A useful report contains:
- the component and the commit or release you tested;
- what an attacker can do, and what they need in order to do it;
- steps to reproduce, ideally on a local network;
- whether you have told anyone else, and when you plan to publish.
Test on a local network
Everything in the repository can be exercised on a disposable network on your own machine, with test keys and without contacting the devnet. See Run a local network.
Please do not test against the hosted devnet in ways that affect other people: no attempts to exhaust the cohort’s finite grants or relay jobs, no denial of service against the gateway, and no access to wallets that are not yours.
In scope
| Component | Where |
|---|---|
| Payment protocol: verification, wire formats, pool state, anchors | protocol/payments |
| Native payment program: execution, staging, nullifier accounts, coin accounting | node/adapter |
| Local modifications to the Agave snapshot | The changed files listed in THIRD_PARTY.md |
| Agave 4.3.2 candidate patches | node/candidate |
| Wallets and their cores | clients |
| Gateway, relay, faucet and admission tools | tools |
| Explorer feed and page | tools/devnet_explorer |
| This website and the hosted devnet wallet | zolana.com and devnet.zolana.com |
The kinds of finding that matter most: creating or spending shielded value that should not exist, spending a note twice, a payment that verifies on one validator and not another, loss or theft of a wallet’s keys, a wallet that can be made to send a different payment from the one reviewed, and anything that reveals payment amounts or recipients that the design says are hidden.
Known limits, not vulnerabilities
These are documented properties of the devnet. Reports are still welcome if you find they are worse than described.
- The gateway operator can link a wallet’s activity. See the privacy boundary.
- Wallets trust their RPC endpoint and do not verify consensus independently.
- The browser wallet is a hosted hot wallet: a compromised site could replace wallet code.
- Fees, timing, nullifiers and deposit or withdrawal amounts are public.
- The chain is not post-quantum secure.
- Every validator is run by the project.
Vulnerabilities in upstream Agave or in the orchard crate that are not specific to this project’s changes should go to those projects.
What to expect
- No bug bounty has been announced.
- No response time is promised.
- If you intend to publish your finding, say when in your report, so that a fix can be discussed first.