Rand Wallet for iOS
A native SwiftUI app over the shared Rust wallet core, linked as an XCFramework. Your spend key stays in the iPhone's Keychain behind Face ID or Touch ID, and the app talks to nothing but the RPC endpoint you choose.
App Store listing pending. Until it clears review, build it from source below.
- Built with
- Swift · SwiftUI
- Distributed through
- TestFlight while in testing, then the App Store
- Requires
- iOS 16 or later
- Sending
- Proves on the phone, or through the RandProtocol prover
Proves on the phone, or through the RandProtocol prover
On a phone with about 8 GB of memory the app proves a transfer on the device. It takes a minute or two, and the Send flow keeps the screen awake and asks you to keep the app open.
A bundle proof peaks at about 6.2 GB. On a phone with less memory iOS would stop the app mid-proof, so the review step warns with the device's own numbers. The phone then uses the RandProtocol prover by default, or your own rand-prover over https (Settings → Prover), and builds the transfer while the prover makes the proof.
A device that cannot make a proof uses the RandProtocol provers by default: a few machines run by the validators (four today, under https://prover.randprotocol.org), no fee. From 0.6.9 each has its own key, which the wallet pins, and the wallet says so before the first send. The machine that proves a send receives the wallet's viewing key and a one-time salt: its operator can read the wallet's whole history, every payment received and sent, and cannot spend. The spend key never leaves your device, which makes the small authorisation proof itself. For more privacy choose your own prover in Settings → Prover, which is then always preferred; the wallet checks every proof before it submits it.
Pairing a prover, step by step: docs/prover.md.
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.
Swap, in the app
From 0.7.1 the phone apps have the Swap screen the extensions and the desktop app have: trade RAND and tokens through the durian.market pools without leaving the wallet. The phone makes the program call's proof and the spend authorisation itself, which needs about 1.5 GB of memory, and the RandProtocol provers make the large proof. The amount you receive is exact; if the pool moves first, nothing is sent and you get a new quote.
Until the App Store listing clears
- Apple installs an app only from TestFlight or the App Store, so there is no file to download for iOS.
- Build and run it from the clients repository in Xcode 16 or later, on a simulator or on your own device.
- randpay: links open the Send screen pre-filled; nothing is sent until you confirm.
Toolchain: Rust 1.98.1, pinned in the repository, which rustup installs. The build guide covers every client from a clean machine. Source directories: ios/, core/.
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)
core/scripts/build-ios.sh # → ios/Frameworks/RandWalletCore.xcframework
open ios/RandWallet.xcodeproj # or build with xcodebuild, below
cd ios && xcodebuild -project RandWallet.xcodeproj -scheme RandWallet \
-destination 'platform=iOS Simulator,name=iPhone 17' buildWhat 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.