For users
Your keys remain Bitcoin keys.
Connect your wallet to Purity
Bitcoin Purity uses the same addresses and transactions as Bitcoin. You do not need a separate Purity wallet — use BlueWallet, Sparrow, or any wallet that lets you point at a custom Electrum server. Your existing seed or keys work on Purity mainnet. Electrum desktop validates Bitcoin mainnet and cannot connect to Purity.
A public Electrum server is available. Enter the settings below in your wallet's network or server preferences.
- Server
electrum.bitcoinpurity.org- Port
50002- SSL
- Yes
- Server string (BlueWallet)
electrum.bitcoinpurity.org:50002:s- Full URL (Sparrow Wallet 2.5.3 or earlier)
ssl://electrum.bitcoinpurity.org:50002- Block explorer
https://mempool.bitcoinpurity.org
BlueWallet
- Open Settings → Network → Electrum Server.
- Paste the server string above, or enter the host and SSL port manually with SSL enabled.
- Set Block Explorer to https://mempool.bitcoinpurity.org.
- Save and let the wallet sync.
Sparrow Wallet 2.5.3 or earlier
- Open Settings → Server.
- Choose Server Type: Public Electrum Server.
- Paste ssl://electrum.bitcoinpurity.org:50002 as the URL.
- Set Block Explorer to https://mempool.bitcoinpurity.org.
- Set Fee Rate Source to Server.
- Apply and let the wallet sync.
This server helps your wallet read the Purity chain and broadcast transactions. It does not hold your keys. Before sending, read the Safety Guide — especially about replay and confirmation depth.
PurityWallet
PurityWallet is the official Android wallet published by Bitcoin Purity. The current release is 1.0.0. Download the APK and its SHA256SUMS file from the official release page, then verify the APK checksum before installing.
Build from source · Android
Install Node.js 24, JDK 17, and Android SDK Platform 36 with Build Tools 36.0.0 and NDK 28.2.13676358. Then clone the published source tag and build a local debug APK:
Clone and build
git clone --depth 1 --branch 1.0.0 https://github.com/BitcoinPurity/PurityWallet.git
cd PurityWallet
npm ci
cd android
./gradlew assembleDebugThe APK is written to android/app/build/outputs/apk/debug/app-debug.apk. This locally built debug APK is for testing and is separate from the official release APK.
Use the official release
For normal installation, use the APK attached to the official release. Compare its SHA-256 value with the matching entry in the release's SHA256SUMS file. A locally built debug APK uses a different signing key and cannot update the official installation.
Continuity
- Bitcoin addresses are unchanged.
- Transaction format is unchanged.
- Sighash remains compatible.
- No transaction-level replay protection is added.
- You do not receive a new token.
Compatibility is not the same as finality.
Because the formats remain compatible, a transaction may be valid on both Purity and a compatible legacy history. That is a design choice with trade-offs. Lack of replay protection is not risk-free.