Download Zecboat
Version 0.7.1-beta · released 13 October 2026
New in 0.7.1
- ✓ Collections: every collection in the on-chain Zecboat Registry, with a Check button (17 checks, read from the chain)
- ✓ Verified badge: “issued by … via Zecboat Registry”, and tiles keep their verified artwork
- ◐ Lineage: each unit’s path back to its mint, carried in the transfer itself (Knotline) · awaiting external review
- ✓ Your node, chosen at setup: a node on this machine, your own node elsewhere, or a public provider
- ✓ YubiKey can seal the wallet’s key file ·
install_yubikey.shis in the zip · it does not protect spending - ✓ Balance itemised: spendable · locked · pending · needs a rescan
- ✓ Postcards locked: an ordinary send never spends them
- ✓ Restore asks for the node first
A wallet without its own node takes the chain’s answers from its provider. Balances, lineage and collection checks are then only as good as that provider’s answers, and the wallet says so: the send screen reads “Chain answers from: your provider”, and a lineage checked that way reads “Lineage checks out · your provider”, never “Verified”. Run your own node and the wallet checks the chain itself.
Beta. No independent security audit.
◐ Known in this beta: if you switch Settings to a node that does not answer, the wallet stays on it until you choose your provider again or restart. Fixed in 0.7.2.
◐ This release does not follow the NU7 network upgrade of 5 November 2026. Update to 0.7.2 before that date.
Zecboat Debian Desktop Wallet
Debian 13. Install: the package plus its scripts. No Node, Rust or -dev packages needed.
zecboat-0.7.1-beta-debian.zip93d8c9171e19f26cc49df76abe19f519ee30e34856560df7cdd8799ac2ba2f9dZecboat_0.7.1_amd64.debinstall.shinstall_depends.shinstall_yubikey.shuninstall_zecboat_deb.shrelease_public_key.hexSHA256SUMSSHA256SUMS.sigunzip zecboat-0.7.1-beta-debian.zip cd zecboat-0.7.1-beta-debian sha256sum -c SHA256SUMS # the .deb and every script, against the signed list bash install.sh
Check what you downloaded before running it: sha256sum zecboat-0.7.1-beta-debian.zip — it must equal the hash above.
After the install, see that the package is in and the binary is the one shipped:
dpkg -s zecboat | grep -E '^(Status|Version)' # Status: install ok installed · Version: 0.7.1 sha256sum /usr/bin/zecboat-ui # b33a781823d09c4ae33a4c758244e85877ab70a2523efcf71ca66a779243768e
Source
Build it yourself and verify what you are running. Needs the build packages, Node 22 and Rust.
zecboat-0.7.1-beta-src.tar.gzae9ff327191d7f73a03b3287c8411d31981a15dfa5764a2e7c8d1ce40fff4cd9tar xzf zecboat-0.7.1-beta-src.tar.gz cd zecboat-0.7.1-beta sudo apt install build-essential pkg-config libglib2.0-dev libgtk-3-dev libwebkit2gtk-4.1-dev \ libayatana-appindicator3-dev librsvg2-dev libssl-dev libxdo-dev # Node 22 and Rust (the version in rust-toolchain), then: cd zecboat-ui && npm install && npx tauri build --no-bundle
Check what you downloaded before running it: sha256sum zecboat-0.7.1-beta-src.tar.gz — it must equal the hash above.
Build from source
The whole wallet is a Rust core and a Svelte interface, built with Tauri. Building it yourself is the only way to know that the binary above matches the code — a signature proves who published a file, not what is inside it.
git clone https://zecboat.com/zecboat.git cd zecboat sudo apt install build-essential pkg-config libglib2.0-dev libgtk-3-dev libwebkit2gtk-4.1-dev \\ libayatana-appindicator3-dev librsvg2-dev libssl-dev libxdo-dev # Node 22 and Rust (the version in rust-toolchain), then: cd zecboat-ui npm install npx tauri build --no-bundle
Use npx tauri build, not cargo build. Cargo compiles the Rust but never embeds the web interface, so the application starts to a blank white window with no error. It is the most common way this build goes wrong.
Expect 30 to 60 minutes, most of it waiting for Rust. The full dependency list and the step-by-step version are in the Debian install guide.
Built binaries are not reproducible between machines yet, so a hash you produce locally will not match the one above. That is expected and is not evidence of tampering.
Circuits, verifier and Knotline
The lineage proof is a separate tree, zmap-wake. The wallet pins the verifying keys built from it; the Wake v1 and Knotline v1 pages are generated from the same tree.
git clone https://zecboat.com/zmap-wake.git cd zmap-wake cargo test
What these checks do and do not prove
| 1 | Download integrity — the file you received is the file whose hash is published. Catches a corrupted or swapped download. | works now |
|---|---|---|
| 2 | Publisher signature — those hashes were signed by a key held offline. Verify it with openssl using a copy of the public key taken from somewhere other than this site: a key served by the same host that serves the download proves only that the two agree with each other. | verify manually |
| 3 | Package integrity — the SHA256SUMS inside the zip verifies the .deb after you extract it. | works now |
| 4 | That the binary matches this source — it would take reproducible builds to show that. Until then, building it yourself is the answer. | not yet |
A signature says a file came from the holder of a key. It does not say the software is safe, audited, or free of defects. Zecboat has had no independent security audit yet.
Why the Debian download is a zip
It is not for compression — a .deb is already compressed, and zipping it saves under half a percent. The zip exists to keep install_depends.sh with the package.
That script fetches the Sapling proving parameters, roughly 50 MB that live in your home directory and belong to no package. Without them Zecboat installs, syncs and shows balances perfectly — and then fails the first time you try to send. That failure looks like a broken wallet and is not one.
So the honest download size is 24 MB for the wallet plus about 50 MB of proving parameters, fetched once on first setup.