XRP Ledger developers propose creating wallets with zero XRP for stablecoin payments

Developers associated with the XRP Ledger are currently testing a mechanism that would permit sponsors to cover the reserve requirements for new accounts, enabling users to begin with zero XRP.

This experimental change, introduced via a code proposal on Oct. 15, involves a transaction named SponsoredAccountCreate. This function allows an established account to create another account while simultaneously covering its initial reserve requirement.

Currently, the XRP Ledger mandates a minimum reserve of 1 XRP per account, which remains locked while the account is active. This prevents the network from accumulating numerous empty wallets, but it necessitates significant capital outlay; for instance, establishing 100,000 accounts would require setting aside 100,000 XRP solely for reserves.

Under the proposed structure, the sponsoring account would absorb the reserve cost, allowing the newly created wallet to maintain a zero XRP balance. Furthermore, sponsors could cover transaction fees through a wider sponsorship framework, enabling applications to pay these charges on behalf of their end-users.

This development builds upon the existing Sponsored Fees and Reserves standard, which permits one account to pay network costs without assuming control over the user's private keys. This new code would thus facilitate account creation without requiring the immediate transfer of any XRP to the new wallet.

Ripple recently entered into a partnership with Privy, a company owned by Stripe, to integrate embedded wallets into XRP Ledger applications. This integration aims to facilitate payments using XRP and Ripple’s RLUSD stablecoin, including automated transactions executed by AI agents.

The current requirement for these wallets to possess XRP funding before activation poses an obstacle, even when their intended use is solely for stablecoin transactions. The proposed transaction directly addresses this by creating the account without transmitting any XRP.

The pull request for this code remains open and faces two unresolved findings from automated code review. Moreover, its activation is contingent upon broader sponsorship amendments that require validator approval; as of Oct. 19, the sponsorship amendment had secured 11 out of the 29 necessary votes from the network's trusted validators.

These technical adjustments suggest an evolving architectural capability within the ledger, addressing friction points related to initial asset provisioning for automated and payment-centric entities interacting with the network.