XRPL Version 3.3.0 Released with Institutional-Focused Amendments Pending Activation
Key Takeaways
- •The XRP Ledger version 3.3.0 introduces four proposed amendments—Confidential Transfer, Batch, Sponsor, and Permission Delegation—targeting institutional use cases around privacy, payments, and real-world asset management.
- •Confidential Transfer would allow institutions to hide balances and transaction amounts for Multi-Purpose Tokens while keeping accounts and asset types publicly visible, addressing a key barrier to institutional blockchain adoption.
- •RWA.xyz data shows approximately $1.38 billion in real-world asset value on the XRPL, with roughly $850 million from Ripple's stablecoin RLUSD and the remaining $530 million from issuers including Ondo, Archax, Societe Generale, and VERT Capital.
- •The Batch amendment would enable grouping up to eight transactions with atomic execution, while the Sponsor amendment would let one account cover another user's transaction fees and reserve requirements.
- •None of the proposed amendments are active on XRPL Mainnet yet, as each requires support from at least 80% of trusted validators for two consecutive weeks before it can be activated.
XRPL Version 3.3.0 Released with Institutional-Focused Amendments Pending Activation
The XRP Ledger (XRPL) has released version 3.3.0, advancing its push to serve as infrastructure for institutional tokenization. The update introduces several proposed amendments targeting privacy, payments, and real-world asset (RWA) management.
Confidential Transfers
The most notable addition is Confidential Transfer, a feature designed to let institutions conceal balances and transaction amounts for Multi-Purpose Tokens (MPTs) while keeping the accounts and asset types involved publicly visible. It relies on cryptographic proofs to validate transactions without exposing the underlying amounts.
According to the project's GitHub post, this capability could resolve a significant hurdle for financial institutions seeking the transparency and settlement advantages of a public blockchain without disclosing sensitive position sizes or transaction values. Institutional reluctance to expose trading activity on public ledgers has been a recurring barrier to blockchain adoption across the industry, with several networks exploring privacy-preserving mechanisms to address it.
RWA.xyz data indicates that approximately $850 million of the $1.38 billion in RWA value distributed on the XRPL comes from Ripple's stablecoin, RLUSD. The remaining roughly $530 million consists of tokenized assets from issuers including Ondo, Archax, Societe Generale, and VERT Capital. The presence of established financial institutions such as Societe Generale among XRPL issuers underscores the ledger's positioning in a competitive institutional tokenization landscape that includes Ethereum, Polygon, and other enterprise-focused chains.
Batch, Sponsor, and Permission Delegation
Version 3.3.0 also includes three additional amendments: Batch, Sponsor, and Permission Delegation.
Batch would permit up to eight transactions to be grouped together, featuring an atomic mode in which either every transaction in the batch succeeds or the entire batch fails. This is expected to support complex settlements, swaps, and institutional workflows.
Sponsor is designed to allow one account to cover another user's transaction fees and reserve requirements. This could enable companies to onboard customers without requiring them to hold XRP before using an application.
Permission Delegation would allow account holders to grant another party predefined transaction permissions without relinquishing full wallet control. The amendment is intended to work alongside Dynamic MPT, giving issuers greater flexibility to modify certain token characteristics after issuance.
Activation Requirements
None of these amendments are live on the XRPL Mainnet yet. Under the ledger's governance process, each amendment must maintain support from at least 80% of trusted validators for two consecutive weeks before activation. If an amendment does not reach the required threshold, it does not activate and has historically been revised or re-proposed in a subsequent release.