What Zolana is
Zolana is an independent Layer 1 blockchain derived from the Agave validator, with shielded payments implemented in the protocol itself. ZOL is the name of its native coin.
It has its own genesis, its own validators and its own coin. The coin pays transaction fees and is the stake asset. Zolana is not a Solana program, token or rollup, and it does not settle on Solana.
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.
What “native” means
The code that checks a shielded payment is part of the validator. It is a built-in program registered in the validator’s own builtin registry and switched on by a feature gate. When a block is executed, every validator verifies the payment’s proof and signatures and applies the result in the same transaction: the shielded pool’s backing, the new note commitments and the permanent nullifier accounts.
A privacy application deployed as a program on top of an existing chain is different in kind: it is application code that the host chain runs like any other program. On Zolana the rules are part of the chain’s own state transition. The practical consequences, all visible in the code, are these:
- The pool is created at genesis. There is no instruction that initialises or replaces it.
- Unmodified upstream validators cannot validate this network’s payments. They do not contain the built-in.
- Other programs cannot call it. The handler rejects any invocation that is not a top-level instruction.
- The pool holds the native coin itself. Deposits move real native coins into the pool account and withdrawals move them out.
- Spent-note records are ordinary accounts. Replay, snapshots and fork choice handle them with the validator’s existing account machinery, not a side database.
“Native” is a statement about where the rules live. It is not a claim that the result is faster or safer than other designs. The cryptography is not new either: payments use the orchard crate (version 0.16.0, Orchard v2 bundles with Halo 2 proofs) unchanged, and the project does not define its own circuit. Using an existing proof system does not make this integration secure.
Privacy is also not a property of every transaction. Public accounts and public transfers still work. A user deposits native coins into the shielded pool, sends privately, and can withdraw to a public account.
What exists today
| Part | State |
|---|---|
| Validator integration | A built-in payment program in an Agave 3.0.14 source snapshot, with tests that run signed transactions through the Agave Bank. A separate patch series ports it to Agave 4.3.2. |
| Shielded payments | Deposit, private send and withdrawal of the native coin. Every payment has exactly two actions. |
| Fees | Three ways to pay: a development sponsor, the user’s own public fee account, or a fee taken from the shielded notes being spent and reimbursed to a relay. |
| Wallets | A command-line wallet, a device-local wallet UI, and a browser wallet that builds proofs and decrypts notes on the device. |
| Network | One public devnet with valueless test coins, operated by the project, running in scheduled windows. |
| Explorer | A read-only page that shows recent blocks and transactions. |
| Tooling | Python tools for local test networks, gateways, faucets, history retention, monitoring and wallet packaging. |
The pages How shielded payments work and Privacy boundary go into detail. Build on Zolana covers the code.
What does not exist
- No mainnet and no production deployment.
- No bridge to Solana or to any other chain, and no exchange, swap or trading function.
- No independent audit of the protocol, the validator changes, the wallets or the operator tooling.
- No independent validators. Every validator of the devnet is run by the project, and they are co-located on one host. There is no procedure for an outside operator to join.
- No post-quantum security. The chain uses Ed25519 and Orchard/Halo 2.
- No production economics. No supply, issuance, fee or rent schedule has been chosen. Every amount in the repository is a development parameter.
The repository’s README keeps the full list under Status and limitations. Network: status, releases and roadmap describes what is in progress.
Origin and licence
Zolana is a fork of Agave, the validator software used by Solana. The directory node/agave is a source snapshot of upstream Agave v3.0.14 (github.com/anza-xyz/agave) under the Apache License 2.0, with local modifications. Upstream licences, copyright notices and attributions inside that tree are retained, and THIRD_PARTY.md records the upstream commit and the list of changed files.
First-party code is under the MIT licence. The project is not affiliated with or endorsed by the maintainers of Agave or Solana; their names are used only to describe where the code comes from.