XRP Ledger has released version 3.3.0, introducing a set of proposed amendments aimed at privacy, payments and the management of tokenized real-world assets. The update is framed as another step in XRPL’s effort to position itself as infrastructure for institutional tokenization.

The most notable proposal in the release is Confidential Transfers, a feature intended to conceal balances and transaction amounts for Multi-Purpose Tokens while still showing the accounts involved and the asset type. However, none of the amendments in v3.3.0 are active on mainnet yet.

Privacy for tokenized assets

Confidential Transfers is designed to let institutions use public blockchain settlement without fully exposing sensitive trading information. Under the proposal, balances and transfer amounts tied to Multi-Purpose Tokens would be hidden, while counterparties and the asset itself would remain visible onchain.

The mechanism relies on cryptographic proofs so that the network can verify a transaction is valid without disclosing the underlying amounts. The stated goal is to address a practical concern for financial institutions that may value public ledger transparency and settlement efficiency, but do not want position sizes or payment values visible to everyone.

Why the change matters for XRPL’s RWA push

The release comes as XRPL continues to build out its role in tokenized real-world assets. According to data cited from RWA.xyz, about $850 million of the $1.38 billion in RWA distributed on XRPL comes from Ripple’s own stablecoin, RLUSD.

That leaves roughly $530 million in other tokenized assets on the network. The source article names Ondo, Archax, Societe Generale and VERT Capital among the notable participants in that segment.

Three other amendments in v3.3.0

Version 3.3.0 also includes Batch, Sponsor and Permission Delegation. Batch would allow up to eight transactions to be grouped together, including an atomic mode where either every transaction in the group succeeds or the whole set fails.

Sponsor is meant to let one account pay another user’s transaction fees and reserve requirements. In practice, that could help companies onboard users without requiring them to acquire XRP before they can interact with an application.

Permission Delegation would allow an account holder to assign specific transaction permissions to another party without handing over full wallet control. The proposal is described as aligning with Dynamic MPT and giving issuers more flexibility by allowing certain token characteristics to be changed after issuance.

Not active on mainnet yet

Despite the new release, these features remain proposals rather than live functionality on XRPL mainnet. Activation depends on the network’s governance process.

Each amendment must hold support from at least 80% of trusted validators for two consecutive weeks before it can go live. The next confirmed step, therefore, is whether the validator set reaches and sustains that threshold for Confidential Transfers and the other amendments included in v3.3.0.

Source: cryptopotato.com