Zolana
ExplorerDocsGitHubOpen wallet

Docs · Project

Network: status, releases and roadmap

How the devnet runs today, what has been released, what is in progress and what is only planned. No dates.

The devnet today

There is one public network: a devnet with valueless test coins for trying the browser wallet.

  • It runs in scheduled windows. Continuous operation is being completed, so the network is paused between windows.
  • It can stop itself. The network shuts itself down when its operational safety checks fail.
  • It can be reset. Earlier test networks have been replaced by fresh ones, and balances can be lost when that happens. The previous pilot’s test balances and transaction history are unavailable.
  • It is run by the project. Every validator is operated by the project, and they are co-located on one host. Independent validators are not supported yet.
  • Access is capped. A small, finite number of test-coin grants and relay jobs limits who can use it.

The repository puts it this way: “Expect it to be offline, reset or withdrawn without notice. No availability is promised.”

Where to look: Status shows whether the network is live and when the explorer was last updated. The Explorer shows recent blocks. The Wallet page says whether the wallet can be opened.

Releases

Releases are published on GitHub with their notes.

v0.1.0

The first tagged release of the public repository. Its notes are on the releases page.

v0.2.0: ledger compression

The devnet keeps its whole ledger. Nothing is pruned, so the stored ledger only grows. This release compresses the large ledger columns with LZ4 and rewrote the existing devnet ledgers once with an offline tool.

Ledger compression on the devnet
MeasurementResult
Each validator ledger, on disk26.1 GiB to 4.1 GiB
All three ledgers78 GiB to 12 GiB
Content digests before and after, every column family, all three ledgersIdentical
Records prunedNone

The rewrite tool records an entry count and a SHA-256 over every key and value of every column family, compacts with LZ4, recomputes the digests and succeeds only if they are identical. It never creates a database, drops a column family or deletes a key.

The release notes are open about what is unfinished: the patch is still kept as a draft outside the candidate’s reconstruction plan, one unit test in the ledger crate was not run on the build host, and on-disk growth per hour with compression on has not yet been measured over a full window. Details are in node/candidate/drafts/ledger-lz4/README.md.

In progress

  • Cohort size. Devnet access is opening in cohorts. The current cohort is limited to 200 wallets while network capacity is being raised.
  • Continuous operation. The devnet runs in windows until continuous operation is completed.
  • Explorer history. The explorer shows recent blocks only; full history search is in progress.
  • Validator code line. The workspace builds against an Agave 3.0.14 snapshot, while single-transaction shielded payments need the Agave 4.3.2 candidate, which is still a separately reconstructed patch series.

None of these has a date.

Planned: a bridge from the Solana token

The site’s token section is the reference wording:

ZOL launches first as a token on Solana, to reach users and wallets where they already are while the Zolana network is in development.

A bridge is planned. Holders will lock ZOL on Solana and mint the same amount on the Zolana network. The bridge is not built yet and has no release date.

Until it exists, the Solana token and the devnet are separate, and devnet coins remain valueless test coins.

Nothing in the repository implements the bridge. The design record that chose an independent chain says a future bridge needs its own design and review of custody, remote-state verification, replay protection, withdrawal rules and failure recovery, and that it “must not be described as inheriting Solana’s settlement security”. The token address is in the token section of the home page.

Planned: post-quantum migration

Zolana currently uses Ed25519 for public, fee and validator authorities and Orchard 0.16 with Halo 2 for shielded payments. Neither is claimed to resist a cryptographically relevant quantum computer.

The repository contains a migration roadmap. Its status line reads “planned research and protocol migration, not implemented”, and “no activation date or algorithm choice is committed”. It has five stages:

  1. Inventory and threat model. List every signature, proof, commitment, encryption and backup scheme in use and separate the threats.
  2. Hybrid wallet authorization prototype. Evaluate standardized post-quantum signatures, starting with ML-DSA as a candidate, requiring both a classical and a post-quantum signature over the same intent.
  3. Validator migration. Versioned hybrid identity, vote and network authentication, with activation rules and key rotation.
  4. Shielded protocol and fund migration. Research a reviewed quantum-resistant design for proofs, commitments, authorization and note encryption, and specify how existing notes migrate.
  5. Reviewed activation. Publish the exact protection scope and procedure after independent review and a rehearsed upgrade.

The roadmap is careful about scope: “Hybrid authorization is a possible first experiment, not full-chain PQ security”, and protecting future signatures “does not retroactively protect previously published ciphertexts”. It promises no generic “quantum-proof” label. Source: docs/post-quantum-roadmap.md.

What stands between this devnet and anything more

The repository lists these as open before any public release beyond a devnet: wallet safety, load testing, archive availability, production parameters and independent review. It also lists as unfinished: a procedure for independent validators, signed wallet packages, phone and Safari testing, and recovery testing beyond process crashes.

This page describes work, not a schedule.

Your privacy
has a boundary.

Zolana is an independent blockchain for native shielded deposits, private transfers and withdrawals. The browser wallet creates proofs and decrypts its own notes locally.

Shielded details

Payment amounts and receiving addresses are protected by proofs. Your spending and viewing keys stay on your device.

Public evidence

Blocks, timing, fees, nullifiers and public deposit or withdrawal accounts and amounts remain visible.

The invited gateway knows your membership and receiving address. It sees your IP address and request timing and can link your submissions. This is not a claim of complete anonymity.

Valueless test coins. No Solana bridge, SOL/USDC deposits, post-quantum protection or audited-security claim.