XRP Ledger Developers Propose Zero-XRP Wallet Creation to Ease Stablecoin Onboarding

Developers working on the XRP Ledger have submitted a code proposal that would allow a sponsoring account to create new wallets and cover their reserve requirements, meaning fresh accounts could hold a zero XRP balance from the outset. The proposal, submitted on 15 October, introduces a transaction type called SponsoredAccountCreate and builds on a broader Sponsored Fees and Reserves standard that permits a third party to pay network costs without gaining control of a user’s private keys.

The practical motivation is clearest for payment applications and automated software. Under current rules, every XRP Ledger account must maintain a minimum reserve of 1 XRP, which remains locked while the account is active. A company spinning up 100,000 accounts faces a six-figure XRP commitment just to meet that baseline before any transaction occurs. The sponsored model shifts that cost to the platform operator, allowing end-users and AI agents to start with stablecoins without acquiring XRP first. Ripple’s recent partnership with Privy, a Stripe-owned embedded-wallet provider, illustrates the demand: those wallets currently require XRP funding even when their intended use is purely stablecoin or AI-agent payments using Ripple’s RLUSD stablecoin.

The proposal remains well short of activation. The pull request carries two unresolved automated code-review findings, and the underlying sponsorship amendment had secured only 11 of the 35 validator votes needed, against a threshold of 29, as of 19 October. Until the broader amendment clears that bar and the new transaction code passes review, neither change can activate on mainnet. Operators considering XRP Ledger as onboarding infrastructure for stablecoin products should treat this as an early-stage proposal with meaningful validator-approval risk still to clear.