About

Zolar makes shielded ZEC usable without unshielding it. It is an access instrument, which in practice is two things: a Zcash wallet that runs in your browser and holds its own keys, and a proof system that turns what that wallet holds into a fact Solana can check. What that fact says is yours to choose: how much you hold, what you disclose, and eventually what you do with it. Your ZEC never leaves the shielded pool, and no wrapped token is ever created.

Mission

Make shielded money useful without ever making it public.

Not by moving it, not by copying it, and not by asking anybody to leave the pool it is already in.

The problem

A ZEC holder can stay shielded and earn nothing, or unshield and become traceable. There is no third choice today, and around 30% of the supply has been sitting behind that choice for years. Zcash runs no contracts of its own, so its TVL is zero. Private money at rest, and nowhere to put it to work.

The missing surface

There is also nowhere to plug in. Zcash has no way for a web page to reach a wallet, so the connect button every other chain takes for granted does not exist there. As of August 2026 the standard for one is still a draft, the grant to build it was filed this month, and neither browser wallet shipping shielded ZEC today serves the Ironwood pool. That will be fixed, and fixing it changes less than it sounds: a connect button hands you a wallet on a page, not something to do with what is in it.

The attempts

wZEC, zenZEC, eZEC, WZEC: one idea, four times. The bridge throws away the thing that made Zcash worth using, and what lands on Solana is the price and nothing else. The demand underneath is real. Around $1.5B of ZEC has moved through intent rails without KYC, while zenZEC, the one of them with a public number, has done around $15M on Solana. People want their ZEC to reach further. They do not want a copy of it.

The solution

Every product in this category so far has tried to bring Zcash to Solana. The premise is backwards. Zcash has a decade-deep shielded pool and viewing keys to prove things about it, and nothing on-chain to spend it on; Solana has execution and liquidity and no privacy worth the name. Neither needs to become the other.

The model

Your money is at the bank. The card holds none of it. You pay at a shop, the shop asks the bank, the bank answers, and the payment goes through. Your money never travelled and your account never moved to the shop. A bridge does the opposite: it withdraws everything as cash and carries the suitcase to another country, and now there are two places it can be lost.

A bridge

Zcashyour ZECSolana

Two copies of your value: the original locked in a contract, a stand-in circulating, and the peg risk, custody risk and hacks that keep following both.

Zolar

Zcasha proofSolana

One copy. Your ZEC stays in the shielded pool and does not move; what crosses is a fact Solana can check.

Nobody issued this card. There is no institution behind it, nothing to freeze and nobody to ask. You make the proof, and anybody can check it without asking permission.

How it works

A proof is built in your browser, because that is where the spending key and the Merkle witness are and neither is allowed to leave the device. A quorum of attesters checks that proof and signs the claim beside the anchor it was checked against, because Solana cannot follow Zcash consensus and cannot tell a real Ironwood anchor from an invented one. Solana checks the quorum's signatures. The proof is published next to the attestation, so anybody who wants to redo the arithmetic can.

What a proof says

There is a note commitment in the Ironwood tree at a stated anchor, its value is at least the amount being claimed, the holder has the key that could spend it, and the claim belongs to one Solana account. Nothing about which note leaves the proof: not the commitment, not its position in the tree, not its value, not the address it was sent to, and not how far above the amount it actually sits.

What it does not say

A proof covers one note rather than a balance, so ten notes of one ZEC prove one and not ten. And it shows that the note was in the tree at that anchor, not that it is still unspent today. Answering the second would mean publishing the value Zcash reveals when the note is spent, which would link that spend to a Solana account months later. That is why an anchor carries an age and an attestation expires.

What it trusts

Solana checks signatures rather than mathematics, so the quorum is trusted for what it signs. What bounds that is publication: a signature the proof does not support is detectable by the first person who looks and attributable to whoever signed it. A relay carries the browser's queries to Zcash and sees an IP address, never a key, a note or a witness. Zcash settles in probability, so an anchor can be reorganised out from under a proof. This is not trustless, and calling it that would be false.

Why Zcash, and not a privacy pool on Solana

Three things Solana cannot produce for itself, and no amount of funding shortens the wait for the first one.

  • An anonymity set that took a decade

    Around 30% of ZEC supply has been shielded for years, and every one of those transactions is cover for the next. That cannot be bought or bootstrapped, and a privacy pool with two hundred people in it is not privacy. Zolar plugs into the real Zcash pool rather than starting another one.

  • Viewing keys

    Cryptographic selective disclosure. What sits in the shielded pool is readable by nobody until you hand somebody a key. Then it is readable by exactly the reader you choose, for exactly the window you choose.

  • No contracts, and a turnstile

    It sounds like a weakness. What it buys is no upgradeable admin, no composability risk, and a turnstile that caps how much value can leave a pool. Zcash's Orchard circuit did carry a soundness bug, disclosed in 2026, and that cap bounds the damage to one pool's solvency rather than chain-wide inflation. The bug was never exploited, so the cap was never tested in anger. It is enforced by consensus rather than promised by a team.

What is written, what is measured, and what has no code yet is listed component by component in the docs.