v0.3.9
Which file do I download?
Normal PC or laptop (Intel/AMD) — Windows, Linux, or an Intel Mac — take the x86_64 file.
The aarch64 / arm64 files are for ARM machines only.
| Your machine | File |
|---|---|
| Windows PC | ZKas-Wallet-windows-x86_64.msi |
| Linux PC (Intel/AMD) | ZKas-Wallet-linux-x86_64.deb or .AppImage |
| Linux on ARM | ZKas-Wallet-linux-aarch64.deb or .AppImage |
| Mac, Apple Silicon (M1–M4) | ZKas-Wallet-macos-aarch64.dmg |
| Mac, Intel | ZKas-Wallet-macos-x86_64.dmg |
| Android | zkas-wallet-0.3.9.apk |
0.3.9 — sends can't be blocked by one bad note, wrong node can't brick the app, seed reveal moved behind your lock
Fixed: "matured note has no witness path" when sending. A rare sequence (a send whose transaction was dropped by the network, returned to your balance later) could leave one note in a state the wallet could no longer build a spend proof for — and any payment that happened to select that note failed outright. Now such a note can never be created in the first place, and if a wallet already has one it is simply skipped: your sends go through using the rest of your balance, and the error message tells you honestly if any amount is temporarily unspendable. (Hosted wallets: already fixed server-side.)
Fixed: entering a wrong custom node address no longer bricks the desktop app. The app used to save the address first and ask questions never — with an unreachable node it waited forever on every launch, and people reinstalled to escape. Now the address is tested before it is saved (a wrong one is refused with the old settings untouched), and if the engine ever does come up dead, the error screen has a "Use the public node" button that recovers in place — no reinstall.
Confirmations count immediately again. A background lookup queue could get clogged by old transactions the chain will never answer for, and one slow request could stall the whole 1-second poll — so a fresh payment sat on "0-conf" far longer than it should. Lookups now run in parallel with hard timeouts, and dead entries stop hogging the queue.
Recovery seed moved to Settings — behind your app lock. "Reveal seed" was one accidental tap away, in whatever room you happened to be standing. It now lives in Settings → Recovery seed, and if you have an app lock set, revealing requires re-entering your PIN/passphrase. No lock set? You get an explicit "I'm somewhere private" confirmation instead.
Android: connect through your own node. Settings → "Node & wallet service" now explains and tests the URL of a self-hosted zkas-walletd (run it next to your node; point the app at it) before saving — a wrong URL is refused instead of breaking the app until reset.
Install notes
- macOS: not notarized yet — System Settings → Privacy & Security → Open Anyway (macOS 15), or right-click → Open.
- Linux AppImage: needs FUSE (
sudo apt install libfuse2); blank window on NVIDIA:WEBKIT_DISABLE_DMABUF_RENDERER=1. - Linux .deb: Ubuntu 22.04+/Debian 12+.
- Windows: SmartScreen → "More info" → "Run anyway". On any crash, attach
%APPDATA%\info.zkas.wallet\crash.log.
Installs over 0.3.5–0.3.8 — same signing key, your wallet is kept.