Rippex Wallet reference for the XRP Ledger

Download the build for your platform, then verify it before installing: compare the SHA-256 checksum with the published value and check the detached signature. A mismatch means the file is not the official release — delete it.

On Windows, run the installer as your normal user; administrator rights are not required. On macOS, move the app to /Applications and allow it on first launch. On Linux, mark the AppImage executable (chmod +x) and run it directly — no system-wide install is performed.

The application stores its wallet file and settings in your user profile directory. Nothing is written outside your home directory, so a portable setup or an encrypted volume works fine.

On first run, Rippex generates a family seed (the string starting with s) and derives the classic address (starting with r). The seed is encrypted with your passphrase and written to the local wallet file. It is never transmitted.

A new address does not exist on-ledger until it is funded with at least the current base reserve. Send the reserve plus the amount you intend to keep from an exchange or another wallet, using the exact address, and include a destination tag only if the sender requires one.

Every account must keep the base reserve to remain active, and each trust line or open offer adds an owner reserve on top. Rippex shows total balance and spendable balance separately so reserves are never spent by accident.

The wallet file is symmetrically encrypted with a key derived from your passphrase. The plaintext seed is only held in memory while the wallet is unlocked, for the duration of a signing operation.

Write the seed on paper and store it in two separate physical locations. With the seed alone you can restore the account in Rippex or in any other XRP Ledger client; without it, no software can help.

Never type or paste the seed into a browser, a chat, a screenshot or a support request. Any party asking for it is attempting theft.

Enter the destination address, the amount and — when depositing to an exchange or hosted service — the destination tag. A missing or wrong destination tag is the most common cause of lost exchange deposits; the ledger delivers the funds correctly, but the service cannot credit your account.

Rippex shows the network fee, the resulting sequence number and the final spendable balance before you confirm. The transaction is signed only after you approve it.

Once submitted, the transaction is validated within a few seconds and becomes final. XRP Ledger payments cannot be reversed or cancelled, so verify the address and tag with a small test amount before a large transfer.

For incoming funds, share your r-address; add the memo or tag your counterparty requests. Rippex lists incoming and outgoing transactions with their ledger index, hash, fee and result code.

Create a trust line by specifying the issuer address, the currency code and a limit — the maximum amount of that asset you are willing to hold from that issuer. The limit is a protection, not a balance.

Each trust line increases your owner reserve, so the spendable XRP balance drops when you add one. Removing an unused trust line (setting its limit to zero once the balance is zero) releases the reserve.

Issued assets carry issuer risk: their value depends entirely on the issuer honouring redemption. Rippex displays the issuer for every balance so an asset is never confused with native XRP.

The default configuration uses a public rippled node. You can replace it with any node URL, including your own validator on the local network, from the network settings.

The client subscribes to ledger streams to keep balances and transaction history current, and resubmits pending transactions when a connection drops. If the node becomes unreachable, the wallet stays usable in read-only state until it reconnects.

Because signing is local, an untrusted node cannot alter a transaction. The worst it can do is refuse to relay it — at which point you switch nodes and resubmit.

To move to a new machine, install Rippex, choose restore, and enter the seed. The account, balances and history are read back from the ledger — nothing but the key is local state.

To keep an encrypted copy, back up the wallet file together with the passphrase stored separately. Restoring the file without the passphrase is not possible.

Test your backup at least once: restore into a fresh installation and confirm the derived address matches the one you expect.

tecUNFUNDED_PAYMENT or tecINSUFFICIENT_RESERVE: the amount plus fee would drop you below the required reserve. Reduce the amount.

terNO_ACCOUNT or actNotFound: the destination address has never been funded, or your own account is not yet activated with the base reserve.

tefPAST_SEQ / tefMAX_LEDGER: the sequence number or the last-ledger window is stale, typically after a disconnect. Refresh and resubmit.

If the client will not unlock, the passphrase is wrong or the wallet file is from a different account — restore from the seed instead of trying variations.