Zecnero wallet 0.2: transparent and Sapling
Update, September 26, 2026: wallet 0.2.1 works without a node of your own. New wallets use the public node at node.zecnero.org, and your own node or a custom node URL are options. It also syncs faster and fixes a frozen window in the desktop wallet. The 0.2.1 release notes and the wallets page have 0.2.1 and what the public node can and cannot see. This post describes 0.2.0.
Wallet 0.2.0 is a testnet beta, in three downloads: a command-line wallet for Linux, the same for Windows, and a desktop wallet for Windows. It holds transparent and Sapling shielded coins, and it runs on the testnet only.
Your node, your keys
The wallet has no light server. It connects to your own zecnerod over loopback, at http://127.0.0.1:18732, and signs in with the node’s cookie file. It refuses any node address that is not loopback.
A new wallet shows a 24-word seed once and keeps its keys in a file encrypted with your passphrase. You can restore from the seed with a birthday height, and import a key printed by zecnero-keygen, so coins you have already mined come with you.
What it does
Transparent and Sapling addresses from one seed, balances and history.
Shielding mined coins. The wallet applies the Mainnet rule on the testnet too: mined coins are moved to your Sapling address before they can be spent. The command-line wallet has
--testnet-allow-unshielded-coinbaseto spend them directly on the testnet, one command at a time.Sends to transparent and Sapling addresses, with a memo of up to 512 bytes to a Sapling address.
Rescans, and restore from the seed.
On the live testnet, mined coins were shielded, sent between wallets with transparent and Sapling addresses, sent with a memo, and restored from a seed, with every balance exact.
Shielding and shielded sends need the Sapling parameters, about 51 MB. The desktop zip ships them beside the program. The command-line wallet downloads them the first time and checks each file against its pinned BLAKE2b-512 hash before using it.
What it does not do yet
Orchard and unified addresses. The node verifies Orchard proofs under the corrected circuit from Zcash NU6.2, and the wallet's libraries already contain that circuit. One line in their network-upgrade table still maps Zecnero's upgrade to the older Orchard revision. An Orchard proof built by the wallet would therefore be invalid, and the node would refuse it: nothing would reach the chain and no coins would be at risk. The fix to that line comes with the upcoming testnet network upgrade. Full Orchard support in the wallet is being built, and it stays off until it passes its tests. Until then the wallet refuses Orchard and unified addresses with a clear error.
Mainnet, which has not launched.
Download and check
The files are in the wallet-v0.2.0 folder of the file host, with a signed checksum list:
zecnero-wallet-linux-x86_64, the command-line wallet for Linux
zecnero-wallet.exe, the command-line wallet for Windows
zecnero-wallet-gui-0.2.0-win64.zip, the desktop wallet for Windows
Check the signature first, then the files, in the folder you downloaded them to:
curl -O https://zecnero.org/zecnero.asc
gpg --import zecnero.asc
gpg --fingerprint 653209A344E75767
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS
The fingerprint must read FFFC 8AC0 2BF7 B4B4 50B4 3B1F 6532 09A3 44E7 5767, the same release key as the node. The wallets page has the full instructions, including the check on Windows.