Zolana’s blockchain is currently in devnet. Devnet test coins are valueless and distinct from the ZOL token issued on Solana. The planned bridge will lock ZOL on Solana and mint an equal amount of native ZOL on Zolana, 1:1. The blockchain code has not yet been independently audited. Zolana mainnet and the bridge are not yet live.
The repository now holds a protocol specification with test vectors, fuzz and property tests, a supply monitor tool, JavaScript readers and a cookbook. What’s new lists each addition with its page and its pull request.
Trying the devnet wallet
You want to open the wallet, receive test coins and send a private payment.
Reading and building the code
You want to understand the implementation, run it and build on it.
Checking whether it is real
You want to know what exists, what is claimed and what is not.
All pages
- OverviewWhat Zolana is, what “native” means, what exists today.
- How shielded payments workNotes, commitments, nullifiers, validator checks, proofs and fees.
- Privacy boundaryWhat is hidden, what is public, what the gateway sees.
- Using the devnet walletCreate, join, receive, send and recover on the devnet.
- ExplorerWhat it shows, its recent-window limit and its signed feed.
- Developer overviewThe developer section: what exists, local development, integration.
- Developer SDKVersion 0.1: offline examples, crates to depend on, a payment inspector, the Wasm build, types and an RPC client.
- JavaScript readersOffline readers for a payment, the pool account, a shielded address and the explorer feed.
- CookbookFive recipes with their commands, code and output, copied from the repository.
- Your first shielded paymentA guided path: your own crate builds, proves and verifies a shielded payment, offline.
- Build and run the codePrerequisites, commands, repository layout and tests.
- Run a local networkA local two-validator network and a shielded payment, step by step.
- Crates and command-line toolsCrates, binaries and their commands, and the browser core.
- RPC and gatewayJSON-RPC methods, access proofs and gateway limits.
- Protocol specificationThe specification in the repository, its test vectors and how they are checked.
- Protocol referenceInstructions, account layouts, wire format, constants, errors.
- Integration guidelinesQuote, build, submit and recover a private payment.
- Testing and verificationFuzz targets, property tests, the protocol copy guard and the supply monitor.
- What does not exist yetNo published packages, no open devnet, and what to do instead.
- Network, releases and roadmapDevnet windows, releases, work in progress, planned work.
- What’s newAdditions to the repository that these docs now describe, with their pull requests.
- FAQShort answers for a sceptical reader.
How these docs are written
Every statement about the protocol, the wallet, fees, limits or the network is taken from the public repository or from text already on this site. Message texts are quoted from the wallet source. Where the repository does not answer a question, the docs say so instead of guessing.
A few statements describe the hosted devnet as the project runs it: the size of the cohort, how a wallet joins, how long a membership lasts and the measured time of a first sync. They are stated by the project. The configuration of the hosted devnet is not part of the repository, and where the repository’s own values differ the pages say so.
Numbers such as fees and grant sizes are development parameters. Timings and test counts quoted in the repository were measured by the project on its own machines; they are not independent benchmarks.
If a page here and the code disagree, the code is right. The repository’s README keeps the authoritative list of limitations.