Pinned Tweet
Private is now native.
Zolana is an independent open-source Layer 1 with shielded payments built into the protocol itself.
Devnet, explorer and code are open: zolana.com
Create your wallet and reply with your Zolana address to receive testnet ZOL.
Every Zolana pull request now runs formatting checks, Clippy with warnings denied, and tests on GitHub Actions.
The first run passed 68 Rust tests and 102 JavaScript tests in 3m 36s.
github.com/zolanacom/zolana/…
Developer SDK 0.1 is on GitHub.
Six offline Rust examples, including a shielded payment demo. The repo also has a Wasm build script for the wallet core, TypeScript types, and a JSON-RPC client.
zolana.com/docs/build/sdk/
PR #6 merged runbook fixes for anchor history and wallet-history pagination.
github.com/zolanacom/zolana/…
Draft PR #5 proposes expanding an active devnet cohort in place and batching RPC request debits.
github.com/zolanacom/zolana/…
The devnet paused for 18 minutes this morning to take and verify a backup. Block production resumed automatically.
The status page now shows why the network is paused, when it’s expected back, and upcoming maintenance.
zolana.com/status/
Five slots a second after the restart. The explorer showed 203 ms on this capture.
Whenever a block includes a shielded payment, validators check its proof during execution.
zolana.com/explorer/
The explorer runs on a signed feed. The web server verifies it, then publishes a read-only snapshot. Your browser reads that snapshot from zolana.com. Validator RPC stays private.
zolana.com/explorer/
Our devnet pauses if its last verified backup gets too old. On purpose.
That limits how much new history is at risk if we have to restore the chain.
How do you prove a smaller ledger is still the same ledger?
Our shrink tool computes SHA-256 over every key and value in each RocksDB column family. It reports success only if the before and after digests match and the rewritten files use LZ4.
github.com/zolanacom/zolana/…
Imagine you have a toy box full of your favourite toys.
You wouldn't want everyone peeking inside to see what's yours right?
So you put a lock on it.
That's what Zolana is trying to do for Solana bring more privacy to blockchain activity while keeping things fast.
Today you pick one:
- Zcash hides sender, recipient and amount but has ~75s blocks.
- Solana privacy tools are fast, but their proofs have to fit inside a program, so they shield less. Helius's default ring hides asset and amount; sender and recipient stay public.
Zolana is the attempt at both: full Zcash-style shielding at 0.2s blocks.
It needs its own chain because Orchard proofs are too heavy for a Solana program. We verify them in the validator itself, so no trusted setup and fees come out of shielded funds.
Replying to @zolanacom
I get the idea of a privacy-focused L1, but I’m struggling to see what’s actually new here.
From the posts and site, Zolana is reusing Zcash’s Orchard + Halo 2 for shielded payments and building it into its own chain. Zcash already has mature shielded transactions, and Solana already has privacy solutions (Helius Privacy Rings etc.). The main difference seems to be “Zcash-style privacy on a fast SVM L1”?
What’s the concrete technical or practical advantage over just using Zcash or existing Solana privacy tools right now? Genuinely trying to understand the differentiation.
Zolana retweeted
Replying to @itsveylo
Today you pick one:
- Zcash hides sender, recipient and amount but has ~75s blocks.
- Solana privacy tools are fast, but their proofs have to fit inside a program, so they shield less. Helius's default ring hides asset and amount; sender and recipient stay public.
Zolana is the attempt at both: full Zcash-style shielding at 0.2s blocks.
It needs its own chain because Orchard proofs are too heavy for a Solana program. We verify them in the validator itself, so no trusted setup and fees come out of shielded funds.
Which parts of the ledger actually compressed? On earlier devnet copies, LZ4 compressed data shreds 8.9x and coding shreds 3.7x. Parity data gave LZ4 less repetition to work with.
github.com/zolanacom/zolana/…
How do you stop a double-spend when the ledger hides which note was spent? Zolana uses a public value called a nullifier. 1/4
To spend the note, the wallet submits a proof and the note's nullifier. The proof ties the nullifier to a valid note while keeping the spent commitment hidden. 3/4
1
3
95
Zolana retweeted
Help someone new to crypto understand Zolana.
Quote this post with your explanation. Your own words with no AI-written entries.
The 10 best entries receive $500 in ZOL each. $5,000 total.
We’ll judge clarity, accuracy and originality.
Entries close Nov 27.
Help someone new to crypto understand Zolana.
Quote this post with your explanation. Your own words with no AI-written entries.
The 10 best entries receive $500 in ZOL each. $5,000 total.
We’ll judge clarity, accuracy and originality.
Entries close Nov 27.
What changes when privacy lives in the validator? We forked Agave to make shielded payments a native part of execution. 1/3
During execution, validators check the payment proof and update the pool backing, note commitments and spent markers together. A failed transaction rolls back the whole update. 2/3
Zolana has its own genesis and native coin. Its validators run a built-in payment program that applies these rules. Here's the design decision. 3/3
github.com/zolanacom/zolana/…
















