The project
Is Zolana a fork of Solana?
Yes. Zolana is a fork of Agave, the validator software used by Solana. The repository contains a source snapshot of upstream Agave v3.0.14 under the Apache License 2.0, with local modifications; the upstream licences and notices are retained, and the changed files are listed in THIRD_PARTY.md. The project is not affiliated with or endorsed by the maintainers of Agave or Solana.
Does it run on Solana?
No. It is an independent chain with its own genesis, validators and native coin. It is not a Solana program, token or rollup and does not settle on Solana.
What did the project add to Agave?
A built-in program that verifies shielded payments during transaction execution, the protocol code behind it, wallets, and operator tooling. The payment code is new project code under the MIT licence. See the overview.
Is the cryptography new?
No. Payments use the orchard crate, version 0.16.0, unchanged. The project does not define its own circuit. Using an existing proof system does not make this integration secure.
Has it been audited?
No. No independent security audit or cryptographic review has been completed.
Is there a mainnet?
Not yet. Zolana mainnet and the planned bridge are not yet live. There is one public devnet.
Is it faster than other chains?
No such claim is made. The shared pool account serialises payments, and the repository states that no throughput figure is claimed.
Privacy
Is it anonymous?
No. A shielded payment hides its amount and its recipient from the public ledger. Blocks, timing, fees, nullifiers and deposit or withdrawal accounts and amounts stay public. The devnet gateway knows your membership and receiving address, sees your IP address and request timing, and can link your submissions. The full list is on the privacy boundary page.
Can the gateway spend my coins?
The wallet’s spending and viewing keys are created and used on your device, and the client flows in the repository do not send them to the gateway or relay. The gateway can refuse to serve you, and it can link your activity. Separately, the wallet is delivered as a web page: a compromised site could replace the wallet’s code.
Is every transaction private?
No. Public accounts and public transfers still work. Privacy is an added native capability, not a property of every transaction.
Is it post-quantum secure?
No. The chain uses Ed25519 and Orchard/Halo 2. A migration roadmap exists and is unimplemented planning.
The devnet
Do test coins have value?
No. Devnet test coins have no monetary value and nothing redeems them. They are distinct from the ZOL token issued on Solana. Balances can be lost when a test network is replaced.
Why does the devnet pause?
It runs in scheduled windows while continuous operation is being completed, and it shuts itself down when its operational safety checks fail. Between windows the explorer keeps the last recorded blocks and the wallet cannot be opened.
Why only 10 wallets today?
Devnet access is opening in cohorts, and the current one is limited to 200 wallets while network capacity is being raised. Each wallet receives a test grant and uses relay jobs, and both are finite.
Can I run a validator?
Not on the devnet. Every validator is run by the project and there is no procedure for an outside operator to join. You can run a local network on your own machine; see Run a local network.
Can I deploy a program or send my own transactions on the devnet?
Not as an outsider. In the repository’s design the devnet is reached through a gateway that serves admitted cohort wallets only, and the path the browser wallet uses can submit shielded payments and nothing else. See What does not exist yet.
Is there a bridge, or deposits of SOL or USDC?
No. There is no bridge to Solana or to any other chain, and the shielded pool holds only the native coin. A bridge is planned and not built; see the roadmap.
The code
Where is the code?
In the public repository on GitHub. Build and run the code has the commands.
Can I reproduce the hosted devnet from the repository?
Not completely. The deployment, enrollment and backup automation used to host the devnet is not included. The repository does let you build the code, run its tests and start a local network.
Are the test results in the docs independent?
No. Where a document says a test passed, it refers to the project’s own runs, and the timings and counts quoted were measured by the project on its own machines.