Skip to content
Open for votingTier AUsability

Sponsor XLS-68

Third parties can cover an account's transaction fees and reserves. Sponsor is open for Mainnet voting but is not enabled yet. The latest response reports support from 10 of 35 tracked validators.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Open for voting
XLS
XLS-68
Enabled
Not enabled

What is the current Mainnet vote?

10 of 35 yes votes; minimum: 29 (current 28%; support >80%)

What does this amendment change?

Why does this amendment exist?

New accounts need XRP for fees and reserves before using an application. Services should be able to cover bounded costs without gaining control over users' keys or assets.

How does the mechanism work?

A sponsor can cover another account's transaction fee, account reserve, or object reserve without controlling its keys or assets. SponsorshipSet establishes prefunded limits for fees and reserves. SponsorshipTransfer ends or transfers reserve responsibility for an account or object.

What changes compared with the predecessor?

BeforeAfter
Each account needed its own XRP for fees and had to cover the reserves of its own ledger objects.Another account can cover specified costs and, depending on the model, cosign each sponsored transaction or pay from a prefunded allowance.

Who is this change relevant to?

XRP holders and users

When the required amendments and application support are available, new users can use an app without their own initial balance for fees and reserves. Sponsorship gives the sponsor no spending authority over their assets.

Wallets and app developers

Apps must represent the second signature, sponsor limits, separate fee and reserve responsibilities, and transfer or termination of sponsorship.

Exchanges and issuers

Services can cover onboarding costs and bound MaxFee, FeeAmount, and RemainingOwnerCount per sponsee. Active obligations tie up XRP and block deletion of the sponsor's account.

Node operators

Nodes maintain additional reserve counters, signature checks, and invariants across all sponsored objects and accounts.

What limitations and risks remain?

  • A sponsor can end reserve coverage only if the sponsored account can cover the reserve itself, another sponsor takes over through SponsorshipTransfer, or the object is deleted. For individual objects, this check requires fixCleanup3_4_0 as well.
  • The sponsor does not own the sponsored account or object and cannot delete it merely because it pays the costs.
  • Deleting a Sponsorship object does not remove existing Sponsor fields from accounts or objects already sponsored. That requires SponsorshipTransfer.
  • Only the global SignerList is supported.
  • A sponsored account must send its remaining balance to the sponsor during AccountDelete.
  • A sponsor can delete its account only after all sponsorship relationships have ended or been transferred.
  • The ledger types allowed to carry a Sponsor field are explicitly limited. Certain shared or internal protocol objects are excluded.

What fee and performance figures does the specification provide?

  • Fee sponsorship can be bounded by MaxFee and a prefunded FeeAmount.
  • Reserve sponsorship moves the reserve obligation to the sponsor without reducing the reserve amount itself.
Technical details: transactions, fields, codes and invariants

Transactions

  • SponsorshipSet
  • SponsorshipTransfer
  • Payment
  • AccountDelete
  • sponsorable transactions with SponsorSignature

Ledger objects

  • Sponsorship
  • AccountRoot
  • sponsorable owner objects

Fields and flags

  • Sponsor / SponsorSignature / SponsorFlags
  • Sponsee / Owner
  • FeeAmount / MaxFee / RemainingOwnerCount
  • SponsoredOwnerCount / SponsoringOwnerCount
  • SponsoringAccountCount
  • CounterpartySponsor / ObjectID
  • tfSponsorshipSetRequireSignForFee 0x00010000
  • tfSponsorshipClearRequireSignForFee 0x00020000
  • tfSponsorshipSetRequireSignForReserve 0x00040000
  • tfSponsorshipClearRequireSignForReserve 0x00080000
  • tfDeleteObject 0x00100000
  • tfSponsorshipEnd 0x00010000
  • tfSponsorshipCreate 0x00020000
  • tfSponsorshipReassign 0x00040000
  • tfSponsorCreatedAccount 0x00080000

API methods

  • account_objects
  • account_sponsoring (Clio API specified by XLS-68)

Result codes

  • temINVALID_FLAG
  • temMALFORMED
  • tecNO_TARGET
  • tecNO_PERMISSION
  • tecINSUFFICIENT_RESERVE
  • tecHAS_OBLIGATIONS
  • tecNO_SPONSOR_PERMISSION
  • telINSUF_FEE_P

Invariants

  • The sum of all SponsoredOwnerCount values must equal the sum of all SponsoringOwnerCount values.
  • Creating a sponsored owner object increases SponsoringOwnerCount and SponsoredOwnerCount together; deleting it decreases both together.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

Sponsor is open for Mainnet voting but is not enabled yet. The latest response reports support from 10 of 35 tracked validators.

Activation requires support strictly above 80 percent for two uninterrupted weeks. A reported raw cutoff is not the minimum yes-vote count: with 35 tracked validators and a cutoff of 28, at least 29 yes votes are required.

Where does it sit within its amendment family?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications