The XRP Ledger released version 3.3.0 this week, a technical update designed to turn the network into serious infrastructure for institutional tokenization. The headline feature is Confidential Transfer, a proposed amendment that would let institutions hide transaction amounts and balances for Multi-Purpose Tokens (MPTs) while keeping account identities and asset types visible to the public.
Why privacy was the hold-up
Institutions have always liked the settlement speed and transparency of a public ledger, but they balked at showing the world their position sizes. Confidential Transfer uses cryptographic proofs to verify that a transaction is valid without revealing the underlying amount. That means a bank can settle tokenized bonds or funds on-chain without leaking how much it actually moved.
It's a direct answer to a problem that has kept big finance on the sidelines. The ledger stays transparent, but sensitive figures stay private.
The numbers behind the push
The timing makes sense. Data from RWA.xyz shows about $850 million of the $1.38 billion in real-world assets on XRPL comes from Ripple's stablecoin RLUSD. The other roughly $530 million in tokenized assets comes from names like Ondo, Archax, Societe Generale, and VERT Capital.
So the base is real, but it's still small. Adding privacy tools is the pitch to bring in more.
What else is in the update
Confidential Transfer isn't the only proposal in v3.3.0. The release also includes three other amendments: Batch, Sponsor, and Permission Delegation.
Batch lets up to eight transactions group together, with an atomic mode where either all succeed or the whole batch fails. Sponsor allows one account to cover another user's transaction fees and reserve requirements, which means a company can onboard customers without forcing them to buy XRP first. Permission Delegation lets account holders grant another party predefined transaction permissions without giving up control of the wallet.
That last one pairs with Dynamic MPT, giving issuers flexibility to tweak token characteristics after they've already launched.
Nothing is live yet
None of these amendments are active on the mainnet. They need at least 80% support from trusted validators for two consecutive weeks before activation. That's a high bar, and it's the next concrete thing to watch. The code is out there, but the network has to decide if it wants it.
