XRPL PR #8606 proposes SponsoredAccountCreate — new accounts with zero XRP

rippled PR #8606, opened on Oct 15, 2026 by developer oleks-rip, adds a transaction called SponsoredAccountCreate that creates a new XRP Ledger account with a 0-XRP balance, backed by a sponsor account that covers the ledger reserve. The PR description reads: "Add new transaction that will create new sponsored account with 0 balance (xrp never touch the account)." Primary source: github.com/XRPLF/rippled/pull/8606; coverage: CoinDesk.

What changes

XRPL accounts today must hold a 1 XRP minimum reserve to exist. The reserve is the structural anti-spam mechanism: creating an account implies writing a persistent object to every validator's ledger, and the ledger charges for that in XRP tied up on the created account.

SponsoredAccountCreate keeps the reserve obligation but shifts who pays it:

1. An existing XRPL account (the sponsor) submits a SponsoredAccountCreate transaction.
2. The ledger creates a new account.
3. The new account's reserve is not debited from the new account — it is tied to a Sponsorship ledger entry owned by the sponsor.
4. The new account starts life with 0 XRP on-balance.

The sponsor retains no control over the new account's keys. The user holds their own master key or signer list from account-create. The sponsor's role is strictly reserve custody.

The dependency

PR #8606 registers a new amendment, SponsorV1_1, in features.macro. The sponsorship ledger entry and its co-signing mechanics come from earlier work on the broader sponsored fees and reserves standard — publicly documented at opensource.ripple.com/docs/xls-68-sponsored-fees-and-reserves. SponsoredAccountCreate extends it to the account-creation path.

Why this matters

XRPL has pitched stablecoin and RWA settlement as a native use case — see Ripple's RLUSD rollout and this month's Moody's A2/P-1 ratings. The reserve requirement has been a friction point:

• A user receiving stablecoin payments needs an XRPL account first.
• Buying 1 XRP as a prerequisite is a UX dead-weight for a user whose purpose is to hold a dollar stablecoin.
• Custodial workarounds break the "self-custodied stablecoin" pitch.

SponsoredAccountCreate lets the issuer or an onboarding partner absorb the reserve, so a user can land on XRPL with a RLUSD balance alone and no XRP. This is the mechanism required for the AI-agent and merchant flows Ripple has described around its Privy-based embedded-wallet integration, which assumes a wallet that is created on-demand with no fiat or XRP top-up step.

Status

• State: open, not merged. One commit (29696f8). Title has been edited twice (first Add SponsoredAccountCreate, then Add CreateSponsoredAccount, now feat: Add SponsoredAccountCreate).
• Automated review: two unresolved findings on the pull request page.
• Validator support for the parent sponsorship amendment: per CoinDesk reporting on the Oct 19 state, below the required threshold — 29 or 35 validators needed depending on which count you read in the article; 11 had voted.
• Mainnet impact today: none. The transaction will not take effect until SponsorV1_1 activates on mainnet, which requires 80% UNL support for two weeks and the PR to merge.

Numbers

What to watch

1. Review progress on PR #8606: whether the automated findings get resolved and the PR heads toward merge, or whether review surfaces an issue with the sponsorship-link rules.
2. Amendment votes: whether SponsorV1_1 crosses the 80% UNL threshold once the PR merges. The pre-merge count (per CoinDesk's Oct 19 figure) is well below.
3. Issuer integration: whether RLUSD's issuer (Standard Custody & Trust Company) or Ripple's embedded-wallet front-end becomes the first production sponsor at scale. The economics of covering reserves for every new RLUSD user is the real test.
4. Fork follow-on: SponsoredAccountCreate is a specific case of the general sponsorship model. Expect subsequent PRs covering sponsored object creation (trustlines, offers) if this one lands cleanly.

Context

XRPL's reserve has been debated since the ledger's early years and raised again at each new asset-type introduction (trustlines in 2013, NFTs in 2022, MPTs in 2025). PR #8606 does not change the reserve itself — the ledger still demands the same obligation — but it decouples who holds the XRP from who holds the account. For a chain pitched as the stablecoin rail for banks and payment providers, that is the gap that was blocking non-custodial onboarding of users whose only asset is a stablecoin. Whether it closes depends on amendment math and the merge calendar, not on any new mechanic beyond the one SponsoredAccountCreate already defines.