ME News reports that on October 15 (UTC+8), XRP Ledger developers submitted a code proposal to introduce a new transaction type called SponsoredAccountCreate, enabling existing accounts to pay the reserve fee on behalf of new accounts, allowing new wallets to be activated with zero XRP balance. Currently, the XRP Ledger requires each account to lock up at least 1 XRP as a reserve.
If the proposal is approved, sponsorship costs and transaction fees will be covered by sponsors, while the network’s overall reserve obligations remain unchanged and users’ private key control is unaffected. This proposal targets stablecoin payment scenarios. Ripple recently partnered with Privy, a subsidiary of Stripe, to introduce embedded wallets for the XRP Ledger, enabling payments in XRP and RLUSD stablecoins—including automated payments initiated by AI agents. Currently, even wallets used solely for holding stablecoins require an initial XRP deposit to activate. The new code builds upon the broader Sponsored Fees and Reserves standard, allowing accounts to be created directly without transferring XRP to them.
The proposal is still far from implementation. According to the report, citing data from the XRPL Dashboard, as of October 19, the sponsorship mechanism amendment—a prerequisite—had received only 11 votes of support from 35 trusted validation nodes, falling significantly short of the 29 votes required for activation. Additionally, the associated pull request remains open, with two unresolved automated code review issues. (Source: Foresight News)
XRP Ledger Developers Propose Zero XRP Account Creation
KuCoinFlashShare
Summary
On October 15, XRP Ledger developers proposed a new SponsoredAccountCreate transaction that enables account creation without the 1 XRP reserve requirement. The sponsor covers transaction fees and reserve costs, while the user maintains full control of their keys. This feature supports stablecoin payments and new token listings through embedded wallets powered by Stripe's Privy. As of October 19, the amendment had received 11 of the 29 required validator votes, with two code review issues still unresolved. Federal Reserve developments and broader market trends may influence the timing of its adoption.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.