Rand Wallet v0.8.1

Built for Rand testnet chain 21 (cut 2026-10-12 on fullnode v0.8.0, c0878c3; genesis ca76c2766ed6090ac6ba5dad86b724dd5d2b80c0edfaed287cd8b129e663ca9a), on fullnode v0.8.0 (c0878c3), which this wallet core vendors — the same chain and core as 0.8.0. The one change is the RandProtocol provers the wallet pins: 0.8.0 wallets can no longer use them, so a browser or phone on 0.8.0 should update.

Testnet software: not audited, not for real value.

Download

you have	file
macOS, Apple silicon	rand-wallet-0.8.1-macos-arm64.dmg
macOS, Intel	rand-wallet-0.8.1-macos-x64.dmg
Windows 10 / 11	rand-wallet-0.8.1-windows-x64.msi (or …-setup.exe, the same app)
Debian, Ubuntu	rand-wallet-0.8.1-linux-x86_64.deb
Fedora, openSUSE	rand-wallet-0.8.1-linux-x86_64.rpm
any other Linux	rand-wallet-0.8.1-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.8.1.zip — unzip, then Load unpacked at chrome://extensions
Firefox 140+	rand-wallet-firefox-0.8.1.zip — Load Temporary Add-on… at about:debugging
Android 8+	rand-wallet-0.8.1-android.apk
to build it yourself	rand-wallet-0.8.1-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.8.1-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.8.1-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 — uses the RandProtocol prover by default (https://prover.randprotocol.org, two 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), or none (docs/prover.md). Details, and how to build every client from source: the README and https://randprotocol.org/clients.

Since v0.8.0

• The RandProtocol provers, re-keyed. On 2026-10-22 the machines behind the four pinned provers (a, archive2, nyc3, sfo3) were lost with the account that hosted them. The pool now runs two members, each with a new key made on its own host: a 4SK4-P64N-XWEN-ZSZZ and b 0XZX-NZ1J-SPMB-GWZN, at https://prover.randprotocol.org/m/a and /m/b. Wallets pin the pool at build time and never fetch it, so a 0.8.0 wallet finds no member answering with a key it trusts and refuses each one — it can still prove on the device, or with a prover you pair yourself. This release pins the two new members (docs/prover.md §8). What they see is unchanged: the wallet's viewing key, never its spend key.
• Nothing else changed: same chain, same core, same keys and note store; no rescan.