XRP Ledger Prepares Five Proposed Amendments for xrpld 3.3.0 Release

What is included in 3.3.0

According to Cooper, the five proposed amendments cover confidential token transfers, batched transactions, delegated permissions, sponsored fees and reserves, and adjustable token settings. She said the package is intended to move the network closer to supporting tokenized assets in practical uses such as transfers, trading, collateralization and settlement.

The planned release follows the activation of fixCleanup3_2_0 on July 29. XRPScan data showed that amendment drew support from 30 of 35 participating trusted validators, or 85.71%. After activation, version 3.2.0 became the minimum software release compatible with the updated mainnet rules, while nodes running version 3.1.0 or earlier became amendment-blocked and could no longer track validated ledgers correctly.

Private token balances and transfer amounts

One of the main proposals, Confidential MPT, would add native privacy features for Multi-Purpose Tokens on XRPL. The design uses elliptic-curve encryption and zero-knowledge proofs to hide token balances and transfer amounts while still allowing authorized verification.

Under the proposal, issuers and token holders could keep transaction data out of public view while granting access to a designated third party such as an auditor or regulator. Cooper said privacy is often a basic requirement for financial institutions considering public blockchain infrastructure.

The article notes that the feature could be relevant to US-regulated institutions evaluating public blockchains for tokenized assets, including banks, broker-dealers and asset managers. At the same time, it would be a technical network function rather than regulatory approval for any particular product or activity.

Atomic settlement and delegated controls

The proposed Batch amendment would let transactions involving multiple accounts execute atomically within a single ledger. In practice, that means every part of the batch must succeed together or the entire operation fails.

That structure could support delivery-versus-payment, where an asset transfer and its corresponding payment settle at the same time. It could also reduce settlement risk in more complex workflows that involve several accounts or different assets.

A separate amendment, Permission Delegation, would allow account holders to grant narrowly defined transaction permissions without handing over full signing authority. The example given is an institution authorizing a treasury or operations team to perform specific actions while keeping issuance keys under separate control.

Sponsored costs and adjustable token terms

Sponsored Fees and Reserves is aimed at easing onboarding by allowing a bank, issuer or platform to cover transaction fees and account reserves for users. Cooper said that approach would let users retain control of their accounts and keys without first having to acquire and manage XRP simply to interact with the network.

The fifth proposal, Dynamic MPT, would allow issuers to modify certain token properties after issuance. The adjustable fields could include transfer fees, metadata and other predefined features. Today, issuers may need to replace a token entirely when important terms change, and this amendment is intended to add limited flexibility instead.

Which fields can ultimately be altered will depend on the final amendment specifications. For now, the next confirmed step is the xrpld 3.3.0 software release itself, after which each proposed amendment would still need separate validator backing before it can go live on the XRP Ledger.