TL;DR
- XRP Ledger developers proposed SponsoredAccountCreate, a transaction that could create zero-XRP wallets while another account covers the user’s base reserve requirement.
- The model could reduce onboarding friction for stablecoin payments, embedded wallets and AI agents while keeping users in control of their private keys.
- The pull request remains open and undeployed, depends on the broader Sponsor amendment, and still requires review and validator approval before eventually becoming available on mainnet.
XRP Ledger developers are reviewing a proposal that would let platforms create sponsored accounts with zero XRP balances while another account covers their reserve requirement. The official pull request introduces a transaction called SponsoredAccountCreate and remains open today. The proposal would shift the reserve burden from the user to a sponsor without transferring XRP into the new wallet, potentially reducing onboarding friction across the Ripple and XRP ecosystem.
Sponsored Accounts Could Remove XRP Funding From User Onboarding
The current design requires a new XRPL account to meet a minimum reserve before it can operate. Under SponsoredAccountCreate, an existing account could create a new wallet whose XRP balance remains at zero while the sponsor carries the corresponding reserve obligation. The network-level reserve would still exist, but responsibility for satisfying it would move away from the end user. That distinction could matter for embedded wallet products designed to hide blockchain-specific requirements from customers.
The proposal is particularly relevant for stablecoin-focused applications because a wallet intended to hold assets such as RLUSD currently still needs XRP funding to become active. A company onboarding 100,000 accounts would otherwise need to allocate 100,000 XRP solely for base reserves under the example described in the reference. Sponsored creation could let users begin with stablecoins while the platform handles the XRP reserve requirement behind the scenes. The approach fits ongoing work around machine-to-machine payments using XRP and RLUSD.
Sponsorship could also extend beyond account reserves. The broader mechanism is designed to let sponsors cover transaction fees, which could allow applications to absorb network costs without taking control of users’ private keys. The user would retain account and key control even when another entity pays the reserve or transaction cost. That model could be useful for automated software and AI agents, complementing XRPL payment tooling for autonomous agents where minimizing wallet-management friction is important.
The code is not ready for mainnet deployment. Pull request #8606 remains open, has unresolved review findings and depends on sponsorship changes that have not activated on the production network. The underlying amendment also still requires sufficient validator support before activation. SponsoredAccountCreate should therefore be treated as proposed infrastructure rather than an available XRP Ledger feature. If ultimately approved and activated, it could change who bears onboarding costs for stablecoin wallets while preserving the ledger’s reserve requirement and users’ control of their accounts.