A new XRPL upgrade could concentrate XRP ownership inside banks instead of retail wallets
Businesses could sponsor millions of accounts, turning XRP reserves into an 기관 balance-sheet obligation.
A proposedXRP Ledger (XRPL)upgrade could let banks and fintechs absorbXRPcosts so customers never need to hold the token.
The Sponsoramendment, based on the XLS-68 Sponsored Fees and Reserves proposal, would let a company pay account reserves and transaction fees for another XRPL user while that customer retains control of their account and private keys.
For financial institutions, the change would remove one of the frictions involved in deploying products on the network: requiring every customer to acquire and manage XRP before interacting with tokenized assets, payments or other applications.
Jazzi Cooper, 리플’s head of product, saidthe feature is designed so a sponsor such as a bank, issuer or platform can cover those costs on behalf of users. That could allow consumer-facing applications and 기관 platforms to keep the underlyingXRP mechanicslargely out of the customer experience.
The trade-off moves to the sponsor’s balance sheet. Account reserves would still need to be covered in XRP, while transaction fees would continue to be paid in the token and destroyed when transactions settle. Businesses could therefore become the XRP holders supporting customers who themselves own none.
The proposal remains some distance from activation. As of press time, XRPScan datashowedonly six validators supporting the amendment, short of the 29-validator threshold, with no activation date scheduled.
The structure would alter who carries the capital requirement without eliminating it.
XRPL currentlyrequiresa base reserve of 1 XRP per account and 0. 2 XRP per standard owner-reserve unit, though validators can change those parameters. Under sponsorship, the XRP allocated to a user’s reserve would remain in the sponsor’s account while the ledger records which party is responsible for the obligation.
A business sponsoring 1, 000 otherwise empty customer accounts would therefore carry roughly 1, 000 XRP of additional base-reserve requirements alongside its own reserve, using current parameters. If those customers instead funded their accounts themselves, the same 1, 000 XRP requirement would be distributed among them.
That distinction could become significant if banks, payment companies or 토큰화 platforms deployXRPL products to millions of customers.
A firm serving 1million users could theoretically carry about 1million XRP of base-account reserve obligations under current requirements, before accounting for trust lines, token-related objects, optional sponsorship relationships, and transaction fees. The actual total would depend heavily on the service design.
출처: CryptoSlate