XRPL Sponsored Reserves: Who Pays the XRP Onboarding Cost? (2026)

By XORA · Published October 12, 2026

TL;DR: XRPL reserve sponsorship shifts the XRP backing requirement to a sponsor without automatically giving the user spendable XRP. With a 1 XRP account reserve and 0.2 XRP owner reserve, our conditional model for 100 accounts with two sponsored objects each requires 141 XRP, or 161 XRP with a separate sponsorship pool entry per user. Sponsor was not enabled in the validated Mainnet ledger checked on October 12, 2026, so these are design calculations, not a claim of Mainnet or XORA availability.

Start with activation, not an announcement

The official sponsorship documentation describes a way for one account to cover another account's transaction fees, reserves, or both. It requires the Sponsor amendment. A published tutorial, working development network example, or supported library field does not establish that the feature is active on Mainnet.

For this article, we queried the public Mainnet API and checked the Amendments ledger entry. At 13:03 UTC on October 12, ledger 107606496 contained 97 enabled amendment identifiers. The published Sponsor identifier was absent. A second public endpoint confirmed that same validated ledger. This is a dated observation; activation must be checked again before implementation.

The practical question is still useful: if sponsorship becomes available on a network you use, how much capital would it require, and where would that capital sit? Our answer separates reserve capacity, actual payments, and fee spending. Combining them into a single onboarding cost hides the part a business must keep available over time.

A reserve obligation is different from a payment

Under the documented design, the sponsor holds the XRP needed for the sponsored reserve while the recipient retains control of their account and keys. Covering a 1 XRP base reserve therefore does not mean depositing 1 XRP into the recipient's balance. An issuer could remove the recipient's need to source reserve XRP without promising a cash reward.

Account creation needs separate attention. The Payment reference defines tfSponsorCreatedAccount for an XRP payment that creates an account: the sender becomes its reserve sponsor. Any XRP actually delivered by that payment is a transfer of value, separately from the reserve responsibility. Existing accounts have a different path through SponsorshipTransfer. Our tables measure the resulting reserve requirement, excluding creation payments and execution fees.

This distinction changes acquisition economics. Giving someone XRP reduces the giver's balance and increases the recipient's balance. Sponsoring a reserve consumes the sponsor's available reserve capacity. Neither should be reported as transaction fee expenditure. A product can have a low visible signup price while still requiring substantial XRP to sustain its users.

The formula, including the easily missed overhead

Our Mainnet server_info checks returned a 1 XRP base reserve and 0.2 XRP incremental reserve, matching the XRPL reserves reference. These parameters can change through validator voting. They are inputs to the model, not permanent protocol constants.

For a sponsor that is not itself sponsored and has no unrelated reserve obligations, let A be sponsored accounts, O be sponsored owner reserve units, and P be optional Sponsorship relationship entries. The documented account reserve calculation reduces to:

The Sponsorship ledger entry is optional when the sponsor signs individual transactions. Creating it supports an advance fee or reserve arrangement, but the entry itself adds one owner reserve unit for the sponsor. One entry per user therefore adds 0.2 XRP per user. That is infrastructure overhead beyond the account and objects being sponsored.

The full protocol formula also accounts for objects a sponsor owns itself, and objects someone else sponsors for it. We exclude those to keep the comparison reproducible. A business with existing ledger activity must add its actual obligations rather than copy our totals as a complete treasury budget.

Onboarding 10, 100, and 1,000 accounts

Assume every user has a sponsored base reserve and two sponsored, chargeable owner reserve units. Eligible objects could be two DepositPreauth entries. For N users, A = N and O = 2N. With individual sponsor signatures and no relationship entries, the result is 1 + 1.4N XRP. With one pool entry per user, it is 1 + 1.6N XRP.

These are XORA calculations from documented reserve rules, not observed adoption statistics. The marginal reserve per additional user is 1.4 XRP or 1.6 XRP. The extra 0.2 XRP is 14.29% of the 1.4 XRP baseline, excluding the shared sponsor base. At 1,000 accounts, a small per user design choice accounts for 200 XRP of continuing reserve capacity.

Do not apply the ordinary trust line exception to this sponsor budget. XRPL documents a conditional exception for an ordinary account's first two trust lines. XLS 68, section 3.15.2, says those exceptions do not carry across to the sponsor. Sponsored units still require the full object reserve. An assumed 0.4 XRP saving per user would underbudget our 1,000 user example by 400 XRP.

Budget fee money separately

The SponsorshipSet reference distinguishes a fee budget from an allowance for owner reserves. A positive FeeAmountDelta moves XRP into the relationship's fee pool. RemainingOwnerCountDelta changes an allowance measured in reserve units. Treating both fields as a spendable XRP balance would misstate liquidity.

Consider a hypothetical 0.01 XRP fee allocation for each of 1,000 users. That creates 10 XRP of fee pool funding, separately from the 1,601 XRP reserve requirement. Together those two allocations require 1,611 XRP before creation payments, setup fees, other obligations, or an operating buffer. This is an illustrative budget choice, not a prescribed minimum or a forecast of actual fees.

The transaction common fields distinguish fee sponsorship from reserve sponsorship, and multisignatures can increase the transaction fee. A service should decide which expenses it covers and cap the permitted fee. A reserve sponsor does not automatically promise unlimited transactions.

Ending sponsorship changes who must provide capital

The SponsorshipTransfer reference defines creation, reassignment, and termination of reserve sponsorship. Ending it returns responsibility to the recipient. Insufficient XRP can prevent the change; the documented check for sponsored objects also depends on the fixCleanup3_4_0 amendment. Exit planning must use the actual rules enabled on the relevant network.

For a simple calculation, start with our 100 account model without pool entries. Assume users independently obtain enough XRP, every required transfer succeeds, all accounts and objects remain, and fees are excluded. Ending sponsorship for 25 users reduces the sponsor requirement by 35 XRP, from 141 to 106. Those users now cover 35 XRP themselves. Across the sponsor and users, the total modeled reserve is still 141 XRP.

If the sponsor pays users to fund that exit, the payment offsets the released capacity. It should not be reported as free capital recovery. Equally, deleting a pool entry does not automatically release reserves for existing sponsored objects. The official transfer tutorial walks through changing the sponsor on an existing entry; an operational exit needs the appropriate changes for each outstanding obligation.

For an operator, the useful measures are active sponsored accounts, chargeable sponsored units, relationship entries, fee pool balances, and capacity available for new users. Registered user count alone cannot answer the reserve question. For a user, the useful question is who supplies the XRP if sponsorship ends. A clear answer matters more than an onboarding screen that simply says free.

Frequently asked questions

Is XRPL reserve sponsorship enabled on Mainnet?

It was not enabled in validated Mainnet ledger 107606496, checked on October 12, 2026. Sponsor was absent from its enabled amendments. The calculations here describe the documented design conditional on network activation; they do not establish current wallet or XORA support.

Does sponsorship give a user free XRP?

Reserve sponsorship changes whose balance must cover the reserve. It does not automatically credit spendable XRP to the user. Any payment amount, funded transaction fee budget, and reserve obligation must be accounted for separately.

How much would sponsoring 100 accounts require?

In our model, each account has two sponsored owner reserve units. At a 1 XRP base reserve and 0.2 XRP per unit, the sponsor requires 141 XRP including its own base reserve. Adding one Sponsorship entry per user raises that requirement to 161 XRP, before fees and operating buffers.

Are the first two sponsored trust lines free?

No. XLS 68 states that reserve exceptions available to an ordinary account do not transfer to its sponsor. Two sponsored owner reserve units therefore add 0.4 XRP per user in this model, even when an unsponsored account could qualify for a trust line exception.

Can a sponsor recover all committed XRP immediately?

No. Ending reserve sponsorship depends on the applicable reserve checks and requires the recipient to take responsibility. Deleting a Sponsorship pool entry does not end sponsorship of existing objects. A sponsor should budget for outstanding obligations and transaction costs during exit.

Related reading: understand XRP transaction expiry and LastLedgerSequence, and how XRPL oracle medians and trimmed means turn inputs into a reported number.

Put the XRP beyond your reserve needs to work

Reserve sponsorship and yield solve different problems. This article does not announce XORA support for Sponsor or sponsored customer accounts. Before allocating XRP elsewhere, keep enough for your own operating needs and evaluate the custody arrangement you would accept. Our XRP yield guide, yield calculator, and security information explain the comparison.

XORA offers up to 22% APY value (15% native XRP yield, treasury-subsidised during a disclosed bootstrap, plus estimated XORA reward value). Returns are never guaranteed. The yield source disclosure explains the model; crypto price changes, custody failures, treasury sustainability, and reward valuation can affect results and cause losses. If that risk fits your circumstances, put your XRP to work instead of leaving it idle on an exchange.