Non-custodial XRP account
The account secret (family seed, s…) is generated on your computer and kept in a local wallet file encrypted with your password. Rippex never transmits or stores it.
Loading
Open source since 2015 · Non-custodial XRP
A quiet desktop wallet for the XRP Ledger. Your secret key is created and encrypted on your own computer — no account, no email, no middleman.
Actively maintained. Rippex is still running and still supported — current builds for Windows, macOS and Linux, full XRP Ledger compatibility, and an open source tree anyone can read. Old wallet files keep working: import your secret key and continue where you left off. See the guide.
About
Cross-platform desktop client · built on Electron and ripple-lib · connects straight to rippled nodes over WebSocket.
Rippex is a non-custodial wallet for XRP that started in Brazil in 2015, when Ripple’s own desktop client was discontinued. It was one of the first community-built alternatives: an open-source, cross-platform client for Windows, macOS and Linux that never asks for an account, an email address or identity documents.
Your secret key is created on your own machine and stored in a wallet file encrypted with your password — nothing is ever uploaded. Transactions are signed locally and only the signed blob is broadcast to the ledger, so the node you connect to never sees your key.
It speaks the XRP Ledger directly: sending and receiving XRP, destination tags for exchange deposits, trust lines and issued currencies, the account reserve rules, and transaction history read from the public ledger. Because the key is yours, a Rippex wallet can also be imported into any other XRPL client at any time.
Features
The account secret (family seed, s…) is generated on your computer and kept in a local wallet file encrypted with your password. Rippex never transmits or stores it.
The client talks to XRP Ledger validators over the public WebSocket API and can be pointed at any rippled server you trust, including your own.
Payments are signed on your machine with ripple-lib and only the signed blob is submitted, so the node you use never handles your secret.
Full support for destination tags required by exchanges and gateway deposits, plus transaction history and balances read straight from the ledger.
Set trust lines, hold gateway-issued currencies (IOUs) alongside XRP, and review the account reserve before you commit a transaction.
One Electron-based build family for Windows, macOS and Linux — no browser extension, no cloud service, runs fine on older hardware.
Security and technology
Rippex is a desktop client, not a service. The account secret never leaves the machine that created it: it is generated locally from a cryptographically secure random source, encrypted into a wallet file with a key derived from your passphrase, and only ever decrypted in memory for the moment a transaction is signed.
Everything after that is plain XRP Ledger protocol work: the signed transaction blob is submitted to a rippled node over an authenticated TLS WebSocket, while balances, trust lines, reserves and history are read back from the ledger itself rather than from any database we operate. Because the codebase is open, each of these steps can be read instead of trusted.
The family seed (s…) and the r-address derived from it are produced locally with secp256k1. No key material, passphrase or backup is transmitted, and there is no server-side account to compromise.
The wallet file is sealed with AES-256 in an authenticated mode using SJCL, with the key stretched from your passphrase through PBKDF2. A wrong passphrase fails authentication instead of returning wrong data.
ripple-lib builds and signs the transaction in the app process; the node receives only the signed blob. Cold Wallet mode goes further and signs on an offline machine that never sees the network.
Every build is published with a SHA-256 checksum so you can prove the binary you run is the one released. Nothing auto-updates silently, and no telemetry or analytics call home.
No wallet can protect an exposed secret key. Write the seed down on paper, keep it away from screenshots, cloud notes and chat messages, and treat anyone asking for it — for any reason — as an attacker.
Download
One desktop build per platform, free and non-custodial: no registration, no email confirmation and no licence key. Your XRP account is created locally on first launch and lives on the public XRP Ledger, not on a server here.
Windows 10 or later · 64-bit
42 MB installer
Download for Windowsripple-wallet-win64-1.5.2.exe
macOS 12 or later · Intel & Apple silicon
39 MB disk image
Download for macOSripple-wallet-macos-1.5.2.dmg
glibc 2.28 or later · portable
44 MB AppImage
Download for Linuxripple-wallet-linux-x86_64-1.5.2.AppImage
Compare the published SHA-256 checksum with the file you downloaded before running it — certutil on Windows, shasum -a 256 on macOS, sha256sum on Linux.
Install with the defaults, then create the wallet: the secret key is generated on your machine and encrypted into a local wallet file with your passphrase.
Fund the new r-address with the XRP Ledger base reserve so the account exists on-ledger; until that payment validates, the overview reports it as inactive.
Download Rippex only from this site. Never install a build received by email, chat or mirror, and back up your secret key on paper before you send any XRP to it.
FAQs
