XRP Wallet Reserve Explained: Why Some XRP Cannot Be Sent

By XORA · Published 13 July 2026

On XRP Ledger Mainnet, the current reserve is normally 1 XRP per account plus 0.2 XRP for each reserve unit in its OwnerCount. A wallet with 40 XRP and an OwnerCount of 11 therefore needs 3.2 XRP in reserve, leaving 36.8 XRP before the transaction cost. The reserve is a protocol rule, not a wallet fee, and its values can change.

Why the XRP Ledger has a reserve

Every active XRP Ledger account and every persistent object consumes storage on servers that keep the shared ledger state. Without a cost, an attacker could create millions of accounts, offers, tickets, or trust lines and force every participating server to carry the data. The official XRP Ledger reserve guide describes the reserve as protection against excessive ledger growth.

The reserve is XRP held in the account, not a payment to a wallet company and not interest earned by validators. Most of it remains in the address. The protocol limits payments that would spend the required amount, while still allowing transaction costs to consume reserve XRP. Removing an owned object normally releases its owner reserve for future use.

Current base reserve and owner reserve

We queried the official XRP Ledger Mainnet public server at 10:20:54 UTC on 13 July 2026. Its server_info response reported validated ledger 105,567,996, a 1 XRP base reserve, a 0.2 XRP owner reserve, and a 0.00001 XRP base transaction cost.

These are Mainnet values at one point in time, not permanent constants. Validators can approve new reserve settings through fee voting, and transaction costs can rise when the network or a submitting server is busy. Other networks can use different values.

The reserve formula wallets use

Normal reserve = 1 XRP + (OwnerCount × 0.2 XRP)

Theoretical sendable XRP = balance minus reserve minus transaction cost

The reliable inputs come from two places. The account_info method returns the account balance and OwnerCount. The server_info method returns the current base and incremental reserve. A wallet can combine them using the validated ledger rather than hard coding reserve numbers that may later change.

For display purposes, a wallet may subtract a slightly larger fee buffer than the current minimum. That can make its sendable figure a little lower than the bare formula. A pending transaction, an unvalidated ledger view, or a newly created object can also create a brief difference between two apps.

Which objects raise OwnerCount?

Common reserve bearing objects include trust lines, exchange offers, escrows, payment channels, tickets, signer lists, checks, NFT offers, NFT pages, and deposit preauthorizations. One NFT page can contain up to 32 NFTs, so the reserve is charged by page rather than by individual NFT. A current signer list normally counts as one unit regardless of how many signers it contains.

Do not assume that every row returned by account_objects adds one to your reserve. That method can include entries linked to the account but owned by somebody else, such as an escrow where the account is only the destination. Legacy signer lists can count as several units, while an oracle can count as one or two units depending on how much price data it stores. OwnerCount is the protocol counter to use.

A worked reserve calculation across account objects

Consider a normally funded account with a 40 XRP balance. It owns two trust lines, three open exchange offers, one escrow, one signer list created under the current reserve rules, and four unused tickets. This example does not use the special low balance trust line exception described later.

1. Owner reserve: 11 multiplied by 0.2 XRP equals 2.2 XRP.
2. Total reserve: 1 XRP base plus 2.2 XRP owner reserve equals 3.2 XRP.
3. Balance above reserve: 40 XRP minus 3.2 XRP equals 36.8 XRP.
4. At the sampled 0.00001 XRP base cost, the theoretical maximum payment is 36.79999 XRP.

How removing objects frees XRP

Reserved XRP is not necessarily stuck forever. If the account uses its four tickets, OwnerCount falls from 11 to 7 and the reserve falls from 3.2 to 2.4 XRP. Cancelling three stale exchange offers lowers it to 1.8 XRP. Finishing or cancelling the eligible escrow lowers it to 1.6 XRP. Returning both trust lines to default settings with zero balances lowers it to 1.2 XRP, because the signer list still counts as one unit.

The full sequence releases 2 XRP of reserve capacity. It does not create yield and it does not change the 40 XRP ledger balance, apart from transaction costs paid during cleanup. It changes how much of that balance can be sent.

Important exceptions and edge cases

The first exception concerns trust lines. Official XRPL documentation says a new account funded with only the 1 XRP base reserve can create its first two trust lines without owner reserve. If the account is funded with more than 1 XRP, the normal reserve applies to those lines. This is a protocol exception, so the simple OwnerCount formula should not be treated as universal in every account state.

Trust lines are shared ledger entries. The reserve can apply to one side, both sides, or neither side depending on balances and settings. Usually the token holder pays it and the issuer does not. A trust line disappears automatically only when both sides are at default settings and the balance is zero.

A signer list created or updated after the MultiSignReserve amendment normally counts as one unit. A legacy signer list can count as two units plus one for each signer. The official SignerList reference says updating the list can adopt the lower current reserve treatment.

Can an account go below its reserve?

Yes, through transaction costs. The network destroys the cost rather than paying it to a validator. If those costs push the balance below the required reserve, the account continues to exist, but it generally cannot send XRP to another address or create new reserve bearing objects. It can still submit transactions that do not increase the reserve if enough XRP remains for the cost.

The transaction cost guide also warns that local load can raise the amount required for submission. A wallet that leaves a small cushion can avoid constructing a payment that becomes invalid before it reaches a validated ledger.

Can the base reserve be recovered?

Most of it can be recovered through AccountDelete if the account meets strict conditions and sends its remaining XRP to another funded account. Some obligations block deletion. The account must also be old enough, own no more than 1,000 objects, and satisfy NFT rules where relevant.

Deletion is not free. The official account deletion guide states that AccountDelete currently destroys at least one owner reserve, which is 0.2 XRP at the sampled settings. That cost can apply even when a validated deletion attempt fails, so this is not a casual cleanup method.

Reserve math is separate from custody and yield

A protocol reserve answers how much XRP a specific on chain account must keep. It does not answer who controls the keys, whether a platform pools customer balances, or how an off chain account records withdrawals. Hosted services may use one or a handful of XRP Ledger addresses with destination tags, so an individual customer ledger does not necessarily have a separate 1 XRP network reserve.

Before depositing, understand the custody model, withdrawal controls, and failure risks. XORA explains its safeguards on the security page, and the broader yield mechanics in how to earn yield on XRP. Crypto values are volatile, custody creates counterparty risk, reserve settings can change, and no yield is guaranteed.

Put the sendable XRP to work

The reserve explains why wallet balance and sendable balance can differ. Check the live Mainnet values, use OwnerCount rather than guessing from object rows, allow for the transaction cost, and remove only ledger objects you understand.

Readers can put XRP to work with XORA for up to 22% APY value, never guaranteed, rather than leave it idle on an exchange. The offer comprises up to 22% APY value, 15% native XRP yield, treasury subsidised during a disclosed bootstrap, plus estimated XORA reward value. Rates and reward value can change, crypto and custody involve risk, and the XORA reward component is not native XRP.