Zolana
ExplorerDocsGitHubOpen wallet

Docs · Use

Using the devnet wallet

Create a wallet, join, receive the test grant, send privately and recover. What each limit and message means.

Before you start

Test coins only. Coins on the devnet have no value and nothing redeems them. The network can be reset, and balances can be lost when that happens.

The cohort is limited. The current cohort has 200 places. While places are free, a new wallet can join with one button. When every place is taken you can still create and back up a wallet, but it cannot join, receive or send until the next cohort opens.

The devnet runs in scheduled windows. Between windows the network is paused and the wallet cannot be opened.

Open the wallet

Start at the Wallet page of this site. It checks the network first and shows one of three states:

  • “The devnet is live.” A button opens the wallet at devnet.zolana.com.
  • “The devnet is paused.” “The network runs in scheduled windows and is between them right now, so the wallet cannot be opened. Wallets and balances are safe. This page updates by itself when the network is back.”
  • “Network status is not available.” The page could not read the status. Try again in a minute.

The wallet runs in your browser. It needs a secure (HTTPS) page, web workers and browser storage; with storage disabled it will not start.

Create a wallet

  1. Choose Create wallet and enter a password twice. The password must be between 12 and 1,024 bytes long.
  2. The wallet creates its keys on your device and saves an encrypted copy in this browser. You should see “Wallet created locally. Save your encrypted recovery file next.”
  3. Choose Save recovery file. The browser downloads a small file named Zolana-encrypted-recovery-date.json.

Keep two things, separately: the recovery file and the password. The wallet says it directly: “Zolana cannot recover a forgotten password.” Browser data can be cleared, so a wallet without a saved recovery file can be lost.

The recovery file holds the wallet’s 32-byte seed, encrypted with your password (XChaCha20-Poly1305, with a key derived by PBKDF2-HMAC-SHA256 at 600,000 rounds). It holds no balance and no note data.

Join and receive the test grant

A new wallet has no access to the network until it joins. On the devnet, joining is one button, Get test coins, under “Join the test network”. No invitation code is needed while the current cohort has free places.

What to expect:

  • The cohort is limited. The current cohort has 200 places. When every place is taken, new wallets cannot join until the next cohort opens.
  • One grant per wallet. The grant is requested once and is tied to the wallet. Restoring the same wallet does not produce a second grant.
  • The grant is small. It is 20,000,000 units, which the wallet shows as 0.02. The wallet currently labels the amount “ZOL”; these are devnet test coins, not the ZOL token issued on Solana.
  • It arrives as a private payment. After joining, the wallet says “This wallet has active testnet access.” The balance appears once the wallet has verified its history (next section).
  • Access can expire. A new membership lasts 30 days. An expired wallet shows “This wallet’s testnet access has expired or been revoked. Keep its recovery file and contact the testnet operator.”

Check your balance

Sync history downloads the network’s recent history, verifies it on your device and saves a checkpoint. Only then does the wallet show a balance:

  • Before a sync: “Not synced. No balance has been verified.”
  • After a sync: “Test coins only. Verified through block N.”
First sync

The first sync takes a while, and the wallet tab must stay in front. A new wallet verifies every block of the devnet’s history on your own device before it shows a balance or lets you send test coins. On 20 November 2026 that was about 190,000 blocks and took between 14 and 25 minutes in a desktop browser. The time grows with the length of the chain; the wallet shows the block it has reached and an estimate measured on your device.

Keep the wallet tab open and in front until it finishes. If you switch tabs, minimise the window or lock the wallet, it locks and an unfinished first check starts again from the beginning. The wallet does not lock for inactivity while the first check keeps making new progress; once it has finished, the usual five-minute idle lock applies. Later syncs continue from the state saved on your device; in one measurement, catching up 14,000 blocks took about a minute.

Sending stays off until history has been verified and saved. The Activity view shows the outcome of your last payment in this session; the wallet states that “a complete transaction list is not available yet”.

Receive

Receive shows your private address. It starts with npriv1. Give it to the sender and keep your wallet open and unlocked; incoming payments are checked while it stays open.

The address is for devnet test coins on this network only. The wallet warns: “Never send SOL, USDC or assets from another chain to this address.”

Send privately

  1. Choose Send, paste the recipient’s npriv1 address and enter an amount in ZOL (up to nine decimal places).
  2. Review payment. The wallet syncs, asks the gateway for a fee quote and shows four lines: Recipient, Amount, Maximum private fee, and Total private balance used. Nothing has been sent or charged at this point.
  3. Confirm private send. The wallet builds the proof on your device, saves the payment, submits it once and then checks finalized history for it.

While it works you will see these steps, in this order:

  • “Creating the private payment proof on this device…”
  • “Saving the original payment before sending…”
  • “Submitting the saved original payment…”
  • “Checking the payment in finalized history…”

A successful send ends with “Payment finalized on Zolana. The recipient’s unlocked wallet can now verify the incoming payment.”

Two things about amounts:

  • The fee comes from your private balance. You need no public coins. The amount and the fee together leave your shielded notes.
  • A payment can spend at most two notes. Your balance is a set of notes, and one payment can combine only the two largest. If the amount plus the fee is more than those two hold, the wallet says “This payment and its private fee exceed the currently spendable amount. Choose a smaller amount.” Send a smaller amount, or send to your own address first to combine notes.

If a send is interrupted

The wallet saves the exact payment before it submits it. If the connection drops, the tab closes or the reply is lost, the payment is not lost and must not be repeated. The wallet shows:

The original payment is saved, but its outcome is not confirmed. Check the original payment before any new send.

Choose Check original payment. The wallet looks for that exact payment in finalized history and ends in one of three states:

Outcomes of checking the original payment
MessageMeaning
“The original payment finalized. Its saved recovery journal is now settled.”The payment went through. Your balance reflects it.
“The original payment expired without execution. Its saved recovery journal is settled.”The payment never executed and can no longer execute. Nothing was spent. You can review a new payment.
“The original payment remains unresolved and saved. No replacement was sent.”The network cannot yet show either result. Wait and check again. New sends stay blocked until this is resolved.

Do not try to work around an unresolved payment by creating another one, clearing browser data or restoring the wallet elsewhere. A payment that has not expired can still execute.

Restore on another browser

Choose Restore wallet, select your encrypted recovery file and enter its original password. The file is opened locally. After restoring, use Check network access and then Sync history.

A restore brings back your identity, not an unfinished send. The wallet’s wording: “Keep the original browser’s data until that payment is resolved.”

Locking

The wallet locks itself after five minutes without activity and when the page is hidden or put in the background. Unlock it with your password. Nothing is sent to a password server; the password only decrypts the wallet saved in the browser.

This is a browser hot wallet. The website and your browser must stay trustworthy while the wallet is open. See the privacy boundary for what the gateway can see.

Messages and what they mean

Wallet messages
MessageWhat it meansWhat to do
“This devnet cohort is full. The first cohort is limited to 200 wallets while network capacity is being raised, and every place is taken. Your wallet is saved on this device, but it cannot join, receive or send on this network until the next cohort opens. Nothing is wrong with your wallet.”All places in the current cohort are taken.Keep your recovery file and password. Join when the next cohort opens.
“This wallet has not joined the devnet yet, so it cannot sync. Use Join the test network first. If the cohort is full, joining reopens when the next cohort opens.”The wallet has no access, so the gateway will not serve it.Join first.
“This test wallet has reached its payment limit. Contact the testnet operator to continue.”Each wallet has a fixed number of private payments. In the cohort tooling in the repository it is 6.Nothing is lost. The wallet can still sync and receive.
“The devnet has reached its shared limit for private payments in this cohort, so no new payment can be sent right now. Sending reopens when network capacity is raised.”The relay has a fixed total number of payments for the whole cohort. In the cohort tooling it is 60.Wait. This is a limit of the network, not of your wallet.
“The testnet request limit was reached. Wait before checking this same wallet again.”The gateway limits requests per wallet and per address.Wait a minute and try again.
“Invitation or access is invalid, expired, revoked or bound to another wallet.”The gateway refused the wallet’s access.Check the code. A code can be tied to one wallet.
“Connection interrupted. Your saved wallet and original payments were preserved. Check this same wallet again.”A request timed out or the network dropped.Retry. If a send was in progress, use Check original payment.
“Finalized RPC state is behind your saved wallet. Recovery will not roll it back.”The gateway is showing an older state than your wallet has already verified.Wait and sync again. The wallet refuses to go backwards.
“The wallet engine did not finish in time. Reload to inspect the original saved state.”A long operation stopped making progress.Reload the page and unlock. Saved data is kept.

Limits at a glance

Devnet wallet limits
LimitValueWhere it comes from
Wallets in the first cohort10This site’s Wallet page and the wallet’s own message
Test grant per walletOne; 0.02 ZOL in the cohort toolingtools/native_cohort_service.py
Private payments per wallet6 in the cohort toolingtools/native_cohort_service.py
Private payments for the whole cohort60 in the cohort toolingtools/native_cohort_service.py
Fee per private payment0.003 ZOL in the cohort tooling; the wallet rejects any quote above 0.1 ZOLclients/browser-wallet/product-worker.js
Notes per paymentAt most twoprotocol/payments/src/verification.rs
Password12 to 1,024 bytesclients/wallet-seed/src/lib.rs
Idle lockFive minutesclients/browser-wallet/app.js
Note

The values marked “in the cohort tooling” are what the repository’s cohort service enforces. The configuration of the hosted devnet is not part of the repository, so treat them as the documented design of the first cohort and rely on the wallet’s own messages for the live state.

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.