Rand Wallet v0.6.8

Built for Rand testnet chain 20, cut 2026-10-01 on fullnode v0.6.8 (c9c9bd3): programs that hold state (RPL-2), transactions bound to their chain's genesis (BIND-1), and a bridge fee taken in zUSD. The wallet core vendors that very build. A wallet from this release refuses any other chain; a v0.6.7 wallet refuses chain 20, so update.

Testnet software: not audited, not for real value.

Download

you have	file
macOS, Apple silicon	rand-wallet-0.6.8-macos-arm64.dmg
macOS, Intel	rand-wallet-0.6.8-macos-x64.dmg
Windows 10 / 11	rand-wallet-0.6.8-windows-x64.msi (or …-setup.exe, the same app)
Debian, Ubuntu	rand-wallet-0.6.8-linux-x86_64.deb
Fedora, openSUSE	rand-wallet-0.6.8-linux-x86_64.rpm
any other Linux	rand-wallet-0.6.8-linux-x86_64.AppImage, or the bare binary in …-linux-x86_64.tar.gz
Linux on arm64	the same four, named …-linux-arm64.…
Chrome, Edge, Brave	rand-wallet-chrome-0.6.8.zip — unzip, then Load unpacked at chrome://extensions
Firefox 140+	rand-wallet-firefox-0.6.8.zip — Load Temporary Add-on… at about:debugging
Android 8+	rand-wallet-0.6.8-android.apk
to build it yourself	rand-wallet-0.6.8-source.tar.gz — this repository and its submodule

iOS has no download (Apple installs only from TestFlight or the App Store); build it in Xcode from the source. rand-wallet-0.6.8-android.aab is the bundle submitted to Google Play, attached for the record; a phone installs the .apk.

Check it

shasum -a 256 -c SHA256SUMS --ignore-missing     # macOS
sha256sum -c SHA256SUMS --ignore-missing         # Linux

Get-FileHash .\rand-wallet-0.6.8-windows-x64.msi -Algorithm SHA256

First launch

Nothing here is signed with a paid developer certificate yet.

• macOS: System Settings → Privacy & Security → Open Anyway, or xattr -dr com.apple.quarantine "/Applications/Rand Wallet.app".
• Windows: SmartScreen → More info → Run anyway.
• Linux AppImage: chmod +x it first.
• Android: signed with this project's upload key, certificate SHA-256 75:22:2E:BF:22:D3:95:80:A5:11:2A:AC:B7:EC:2E:03:93:91:07:77:96:E0:45:1D:7B:CF:E3:7E:FA:06:53:52.

A device that can make a proof (the desktop app, about 8 GiB) makes it. One that cannot — a browser, most phones — now uses the RandProtocol prover by default (https://prover.randprotocol.org, four machines run by the validators, no fee), after a one-time notice: like any prover it is sent the wallet's viewing key, so its operators can read the wallet's whole history, and it can never spend. Settings → Prover chooses your own prover instead (the desktop app's Prove for my other devices, or your own server), which is then always preferred, or none (docs/prover.md). Details, and how to build every client from source: the README and https://randprotocol.org/clients.

Since v0.6.7

• The RandProtocol prover is the default wherever the device cannot prove — every browser wallet and most phones can send out of the box. A one-time notice before the first send says what it sees (the viewing key: the whole history, never the spend key); Settings → Prover picks your own prover or none. A submit that never reached the prover is offered again (three tries), and a busy pool is said plainly. Firefox asks its data-collection consent first.
• window.rand.invoke in the browser extensions: a site (durian.market) asks the wallet to call a program; the wallet's own window shows what leaves the wallet and what comes back, the fee and the site, and on Approve proves and submits. Everything a swap can be refused for — a stale pool, a vault that cannot pay, notes that cannot pay in, a chain without programs — is refused before any proof, with a code the site understands.
• Bridge fees (chain 20): the chain keeps 0.1% of each deposit and each withdrawal, in zUSD. A deposit arrives net of it; the withdraw review shows the fee and what arrives. The fee recipient's wallet finds its fee notes (they carry no envelope) by rebuilding them.
• BIND-1: on every chain after 19 a transaction binds its chain's genesis hash, so it is valid there and on no other chain. Every client sends the genesis with each proof.
• Unlock with Touch ID (Chrome extension): a passkey seals your password; the lock screen asks for your fingerprint first, and the password still works.
• The side panel is the extension's home: the toolbar button opens it, in Chrome and Firefox alike.
• The desktop prover host carries the fullnode's Plonky3 fixes (a spin lock held across parallel work, in two places) — with the newer fullnode's parallel proving, without them a desktop proof could hang.
• A new store summary.