What to Know
- XRP Ledger developers are testing a transaction called SponsoredAccountCreate that would allow new wallets to be created with zero XRP.
- The proposal would let an existing sponsoring account cover the required account reserve for a newly created wallet.
- XRP Ledger currently requires a minimum reserve of 1 XRP for each active account.
- A company creating 100,000 separate accounts would need to set aside 100,000 XRP under the current reserve structure.
- The proposed design would keep the network reserve obligation in place while shifting the cost from the end user to the sponsor.
- Sponsors could also cover transaction fees through a broader sponsorship mechanism without taking control of users’ private keys.
- The code proposal was submitted on Oct. 15 and remains under review with two unresolved automated code-review findings.
- The broader sponsorship amendment had secured 11 validator votes as of Oct. 19, below the 29 votes required for approval.
- The proposal could be useful for stablecoin payment applications, embedded wallets and automated payments involving AI agents.
Developers Explore Sponsored Wallet Creation
XRP Ledger developers are testing an experimental account-creation change that could make it easier for payment applications to onboard users who do not already hold XRP. The proposal introduces a transaction known as SponsoredAccountCreate, allowing an existing account to create a new wallet while also covering the reserve requirement tied to that wallet. In practical terms, the new account could begin with a zero XRP balance, even though the ledger’s reserve requirement would still be satisfied by another party.
The change is aimed at a familiar challenge in blockchain-based payments: users often must acquire a network’s native asset before they can activate an account or move other assets. On XRP Ledger, each account currently requires a minimum reserve of 1 XRP. That reserve remains locked while the account is active and is designed to discourage spam, reduce unnecessary account creation and protect the network from being flooded with empty wallets.
For individual users, a reserve requirement may appear modest. For companies building large-scale payment products, however, the requirement can become a meaningful operational cost. A company creating 100,000 separate accounts would need to set aside 100,000 XRP just to meet reserve rules. The proposed sponsored model would not remove the reserve from the system. Instead, it would move the obligation to a sponsoring account, allowing users to interact with wallets that are active without first receiving XRP.
Why Zero-XRP Wallets Matter for Stablecoins
The proposal could be especially relevant for applications focused on stablecoins. If a user wants a wallet only to receive or spend a stablecoin, requiring that user to first obtain XRP can introduce friction. Payment apps often compete on simplicity, and each additional step in onboarding can reduce adoption. A sponsored reserve model could allow a user to start with a stablecoin balance while the application, issuer or platform handles the underlying network cost.
That structure could help make XRP Ledger-based payments feel more like mainstream financial apps, where users are not typically asked to understand technical network funding requirements before making a transaction. Market participants watching the proposal see it as a potential usability upgrade rather than a change to XRP Ledger’s basic economics. The reserve still exists, but the user experience could become less dependent on direct XRP ownership at the moment a wallet is created.
Stablecoin payments are a major use case for this type of design because the intended unit of account may not be XRP. Ripple’s RLUSD stablecoin is one example of the kind of asset that could be used in XRP Ledger payment applications. If wallets are intended primarily to hold stablecoins, developers and businesses may prefer a model where reserve and fee costs are handled invisibly by the service provider instead of passed to the customer upfront.
Embedded Wallets and AI-Agent Payments
The timing of the proposal also intersects with growing interest in embedded wallets and automated software payments. Ripple recently partnered with Stripe-owned Privy to bring embedded wallets to XRP Ledger applications. That integration is intended to support payments using XRP and Ripple’s RLUSD stablecoin, including automated payments made by AI agents.
Embedded wallets are designed to make crypto infrastructure less visible to the end user. Instead of asking users to install separate wallet software, manage every technical detail and fund an account with a native token before doing anything else, applications can build wallet functionality directly into the product experience. Sponsored account creation would fit that model by allowing a platform to activate user wallets while maintaining user control over private keys.
AI-agent payments add another layer of relevance. Automated software agents may need to make small or frequent payments, interact with services, or manage balances without a human manually funding each wallet with XRP. If every agent account needs a separate initial XRP allocation, scaling such systems could become operationally cumbersome. A sponsored reserve and fee model could make it easier for businesses to manage many accounts while keeping users or automated agents from having to hold XRP at the start.
How the Sponsored Model Would Work
The SponsoredAccountCreate transaction would allow an existing account to create another account without sending XRP to that new wallet. The sponsor would carry the reserve requirement, meaning the network would still recognize that the newly created account has its required reserve covered. The new wallet would have a zero XRP balance, but it would not be an unbacked account from the network’s perspective.
The proposal builds on a broader Sponsored Fees and Reserves standard. That broader framework is intended to let another account pay network costs on behalf of a user without controlling the user’s private keys. This distinction is important. Sponsorship, as described by developers and technical traders following the ledger’s evolution, is not the same as custody. The sponsor may pay the required reserve or transaction fees, but the user’s private-key control remains separate.
That separation could matter for companies trying to design compliant and user-friendly payment tools. A platform may want to subsidize onboarding costs without taking possession of user assets. It may also want to pay transaction fees to improve the user experience. In traditional web applications, companies often absorb infrastructure costs directly. Sponsored fees and reserves could create a similar pattern for certain XRP Ledger applications, while still preserving blockchain account ownership at the wallet level.
Validator Approval Remains the Key Hurdle
The proposal is still experimental and should not be treated as an active mainnet feature. The code proposal submitted on Oct. 15 remains open, and two unresolved automated code-review findings are still attached to it. In addition, SponsoredAccountCreate depends on broader sponsorship changes that have not yet activated on mainnet.
Those changes require validator approval. As of Oct. 19, the sponsorship amendment had 11 votes from trusted validators, short of the 29 required for approval. That gap means the timeline for activation remains uncertain. XRP Ledger amendments generally require broad agreement from validators because they can alter how the network processes transactions and enforces rules.
For businesses evaluating XRP Ledger payment architecture, the proposal may be worth monitoring, but it is not yet something that can be relied upon in production planning. Technical traders and infrastructure developers are likely to watch validator support closely, since approval would signal that the network is ready to adopt a more flexible model for account reserves and transaction-cost sponsorship.
Potential Impact on XRP Ledger Adoption
If implemented, sponsored account creation could reduce onboarding friction for consumer payment apps, enterprise wallet deployments and automated payment systems. By allowing wallets to begin without a direct XRP balance, the XRP Ledger could become more accessible to users whose primary interest is stablecoins or application-specific payments rather than holding the native asset.
The proposal does not eliminate XRP’s role in the network. XRP would still remain central to XRP Ledger’s fee and reserve design. What changes is who bears the cost at the point of account creation. Instead of every end user needing to acquire XRP first, businesses could handle the reserve requirement in the background. That could make XRP Ledger-based apps easier to use while keeping anti-spam safeguards intact.
For developers, the sponsored model may also simplify mass wallet creation. A platform that needs to create a large number of accounts could centralize reserve management through sponsoring accounts rather than distributing XRP into each user wallet. That could improve operational control and reduce the complexity of onboarding large customer bases or fleets of software agents.
The key question now is whether validators will support the broader sponsorship amendment and whether the current code proposal can clear review. Until then, SponsoredAccountCreate remains a promising but unactivated feature. Still, the direction is clear: XRP Ledger developers are exploring ways to make blockchain payments feel less technical, more flexible and better suited for stablecoin-first applications.
Frequently Asked Questions (FAQs)
What is SponsoredAccountCreate on XRP Ledger?
SponsoredAccountCreate is a proposed XRP Ledger transaction that would allow an existing account to create a new account while covering that new account’s reserve requirement. The new wallet could begin with zero XRP, while the sponsor carries the required reserve obligation.
Does the proposal remove XRP Ledger’s reserve requirement?
No. The proposal would not remove the reserve requirement. XRP Ledger currently requires a minimum reserve of 1 XRP for each account, and the proposed system would keep the reserve obligation in place while shifting the cost to a sponsoring account.
Why would zero-XRP wallets help stablecoin payments?
Zero-XRP wallets could reduce onboarding friction for users who only want to hold or use stablecoins. Instead of acquiring XRP first just to activate a wallet, users could begin with stablecoins while an application or sponsor handles the reserve requirement.
Could sponsors also pay transaction fees?
Yes. The proposal is connected to a broader Sponsored Fees and Reserves standard that could allow another account to cover transaction fees for users. The goal is to let sponsors pay network costs without taking control of users’ private keys.
Is this feature already live on XRP Ledger mainnet?
No. The code remains under review, and the broader sponsorship changes have not activated on mainnet. The proposal also had two unresolved automated code-review findings, meaning additional review is still needed before any possible activation.
How much validator support does the sponsorship amendment need?
The sponsorship amendment requires 29 validator votes for approval. As of Oct. 19, it had secured 11 votes from trusted validators, leaving it short of the threshold needed for activation.
How could companies benefit from sponsored account creation?
Companies could create large numbers of wallets without placing XRP directly into each account. For example, under current rules, creating 100,000 accounts would require setting aside 100,000 XRP for reserves, while a sponsored model would let the company manage that obligation through a sponsor.
Does sponsorship mean the company controls the user’s wallet?
No. The proposed sponsorship framework is designed to let another account pay reserve and fee costs without controlling the user’s private keys. That distinction allows a sponsor to cover network costs while the user retains wallet control.
Why are AI-agent payments mentioned in this proposal?
AI-agent payments may involve automated wallets that need to send or receive value without manual funding steps. Sponsored reserves and fees could make it easier for applications to support those automated wallets, especially when the wallets are intended to use stablecoins rather than hold XRP directly.