For users
Your keys remain Bitcoin keys.
Recommended wallets
Use PurityWallet on Android or desktop to view balances and send on Purity mainnet.
PurityWallet · Android
The recommended Android wallet for Bitcoin Purity. Download the APK from the release page and verify its checksum before installing.
PurityWallet · Desktop
The recommended multi-platform desktop wallet for Bitcoin Purity. Choose the package for your operating system from the release page.
Alternative wallets
BlueWallet is a mobile alternative, and Sparrow Wallet 2.5.3 or earlier is a desktop alternative. Both require a custom Electrum server. 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
Mobile alternative · 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.
Desktop alternative · Sparrow Wallet 2.5.3 or earlier
- Open Settings → Server.
- Choose Server Type: Private Electrum.
- 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.
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.
