XRP Ledger Upgrade Proposal Adds Privacy Tools for Tokenized Assets

XRP Ledger version 3.3.0 introduces proposed amendments aimed at institutional tokenized assets, led by a Confidential Transfers feature for encrypted balances and payment amounts. The changes are not live yet and need sustained validator approval before activation.

XRP Ledger Upgrade Proposal Adds Privacy Tools for Tokenized Assets

What happened?

XRP Ledger version 3.3.0 introduces proposed amendments aimed at institutional tokenized assets, led by a Confidential Transfers feature for encrypted balances and payment amounts. The changes are not live yet and need sustained validator approval before activation.

Why it matters

The development matters because XRP Ledger is already being used for tokenized real-world assets, and the proposed privacy layer targets a common institutional concern: exposing position sizes and transfer amounts on public blockchain infrastructure. According to CoinDesk, RWA.xyz tracks about $1.38 billion of distributed real-world assets on XRPL, including $845.7 million in RLUSD and more than $530 million in tracked assets outside RLUSD.

A new XRP Ledger software release has introduced six proposed amendments, including a Confidential Transfers feature designed for institutional use of tokenized assets. The proposal would let certain Multi-Purpose Token balances and payment amounts be encrypted while keeping account information and token types visible on the ledger.

The development matters because XRP Ledger is already being used for tokenized real-world assets, and the proposed privacy layer targets a common institutional concern: exposing position sizes and transfer amounts on public blockchain infrastructure. According to CoinDesk, RWA.xyz tracks about $1.38 billion of distributed real-world assets on XRPL, including $845.7 million in RLUSD and more than $530 million in tracked assets outside RLUSD.

The proposed Confidential Transfers amendment is limited in scope at launch. Holders would need to opt in, and the feature would initially apply to direct Multi-Purpose Token payments between accounts. It would not cover trades on XRPL's built-in exchange, escrow or checks.

Other amendments in version 3.3.0 are also aimed at institutional workflows. Batch would allow up to eight transactions to be packaged together, including an all-or-nothing mode. Sponsor would let one account cover another account's fees and reserve requirements, while Permission Delegation would allow limited authority for specified transaction types. Dynamic MPT would let issuers change certain token properties after issuance.

None of the amendments are active yet. XRP Ledger amendments require at least 80% support from trusted validators for two continuous weeks before they can go live, leaving adoption dependent on the validator vote and whether issuers already using XRPL choose to apply the new privacy features.

Source: CoinDesk

Keep exploring

Related stories

Trump Media Pulls Back From Crypto Treasury and Prediction Market Plans

Trump Media Pulls Back From Crypto Treasury and Prediction Market Plans

Trump Media is unwinding two Crypto.com ventures tied to a crypto treasury strategy and prediction markets. The move comes as new leadership redirects attention toward media, data licensing, and a planned merger with fusion energy company TAE.

Read
Trump Media Scraps Crypto.com CRO Treasury Deal

Trump Media Scraps Crypto.com CRO Treasury Deal

Trump Media, Crypto.com and Yorkville Acquisition have ended plans for a public company focused on accumulating and staking Crypto.com’s CRO token. The pullback also includes a separate ETF servicing arrangement, marking a shift away from parts of Trump Media’s earlier crypto expansion.

Read
Developer Warns Bitcoin Holders About Replay Risk From Possible BIP-110 Fork

Developer Warns Bitcoin Holders About Replay Risk From Possible BIP-110 Fork

Bitcoin developer Kevin Loaec warned that holders could lose real BTC if they try to sell coins created by a possible BIP-110 fork before the chains are safely separated. The risk centers on replay attacks, because both chains may initially accept the same signed transactions.

Read