Rand Wallet for Linux
The desktop app: the shared wallet interface in the system webview, over the Rust core linked directly. It is the one client that proves a transfer on your own computer, and it can prove for your browser wallet too.
Version 0.8.0, 2026-10-12. Check the download against its SHA-256 before you open it.
- Built with
- Tauri · Rust core, shared interface
- Distributed through
- a .deb, an .rpm, an AppImage or the bare binary, from GitHub Releases
- Requires
- webkit2gtk 4.1; 8 GiB of memory to send
- Sending
- Proves on this computer
Version 0.8.0
The files are attached to the v0.8.0 release on GitHub; the buttons here are links to them, and nothing is served from this site.
- Debian and Ubuntu: sudo apt install ./ followed by the .deb's name. Fedora and openSUSE: sudo dnf install ./ (or zypper install ./) followed by the .rpm's name. Both pull in webkit2gtk 4.1.
- AppImage: chmod +x the file and run it. Nothing is installed.
- The .tar.gz is the executable on its own, for a distribution none of those fit. It needs the distribution's webkit2gtk 4.1 package, and the INSTALL file inside says where the binary, the icon and the launcher entry go.
- It is the same interface the browser extension shows, in a native window.
# with SHA256SUMS downloaded into the same folder as the file
shasum -a 256 -c SHA256SUMS --ignore-missing # macOS
sha256sum -c SHA256SUMS --ignore-missing # Linux
# or print the sum of one file and compare it with the one above
shasum -a 256 rand-wallet-0.8.0-linux-x86_64.debA matching sum says the file is the one that was published. It does not say the file was built from the source: the builds are not reproducible bit for bit yet, so if that is what you need to know, build it yourself.
Proves on this computer
The desktop app is the one client in which a transfer is proved end to end on the machine you are holding. The wallet core is linked into the app as a Rust crate, so the prover runs natively and the only limit is the machine's memory: a bundle proof peaks at about 6.2 GB, and below 8 GiB of RAM the app declines to start one rather than be stopped half-way through.
A proof takes about a minute on a laptop CPU. The Send screen reports each step (selecting, witness, proving, submitting, confirming), and the auto-lock waits for a transfer in flight instead of dropping the key mid-proof.
The desktop app also proves for your other wallets. Settings → Prove for my other devices gives a pairing link that the browser extension or the local web wallet on the same machine pastes into its Settings → Prover.
Where the key lives
The spend key is the wallet's one secret. There is no account and no server holding a copy: lose the key and nobody can restore it, so save it when the wallet shows it to you.
What the desktop app does not do
Bridge burns, staking, contract deploys and confidential calls are not in the app. Export the key file from Settings and use the rand command-line wallet from the full node repository for those; the same key works in both.
Or build it yourself
- Install the libraries the app links against and the packaging tools (Debian and Ubuntu names below; other distributions carry equivalents), rustup and Node 22 or later.
- The first build compiles the prover and takes several minutes.
Toolchain: Rust 1.98.1, pinned in the repository, which rustup installs. The build guide covers every client from a clean machine. Source directories: desktop/, ui/, core/.
sudo apt install build-essential libwebkit2gtk-4.1-dev libayatana-appindicator3-dev \
librsvg2-dev patchelf rpm file
git clone --recurse-submodules https://github.com/randprotocol/clients.git && cd clients
git checkout v0.8.0 && git submodule update --init # the release; core/vendor/fullnode @ v0.8.0 (c0878c3)
cargo install tauri-cli --version "^2.0.0" --locked # once
scripts/release/build-desktop.sh # AppImage, .deb, .rpm, .tar.gz → dist/release/
cd desktop/src-tauri && cargo tauri dev # or run it from sourceWhat it does, on every platform
- Create a wallet
- A spend key generated on the device, shown once for you to save, and the rand1… address derived from it. Import an existing key, or a wallet.key.json from the rand CLI; every client exports the same file.
- Receive and send
- Your balance is the set of notes only your key can open; the wallet scans the commitment tree to find them. A transfer of RAND or of any listed RPL token is one 4-in-4-out bundle authorised by a proof. Nobody learns the sender, the receiver, the amount or which asset moved.
- Faucet
- On a testnet with an open faucet, one tap mints 100 RAND into a note only you can open.
- Disclose only what you choose
- Copy your viewing key and open My history on RandScan to see every note you sent or received, or copy one payment's transaction key to disclose exactly that payment and nothing else. The explorer decrypts in your browser and never sends the key anywhere.
Viewing keys and transaction keys open on randscan.org.
Before you send anything
- Chain
- The public endpoint serves chain 21, live since 12 Oct 2026 10:31 UTC (cut on fullnode v0.8.0). The wallet core vendors fullnode v0.8.0 (c0878c3) and refuses any other chain: chain 21 runs constraint set 9, so a 0.7.x wallet cannot send on it, and this release cannot send on chain 20. Keys and addresses carry over; a wallet that scanned chain 20 shows a different-chain banner once and rescans from chain 21's genesis. Bridge deposits and withdrawals keep a 0.1% fee in zUSD, which the wallet shows before you withdraw.
- RPC endpoint
- Settings → Network. Defaults to https://rpc.randprotocol.org; any rand-node RPC you can reach works, and a saved URL is checked before it is kept
- Proving
- A bundle proof peaks at about 6.2 GB of memory and takes about a minute on a laptop CPU
- Status
- Experimental testnet software. Not audited. RAND on the testnet carries no real value
- Licence
- GPL-3.0-only, like the full node crates every client links
One wallet, every platform
The same key file, address format and rules everywhere: a wallet created here imports into any other client and into the rand CLI.