XRP Ledger developers are preparing five proposed amendments for the upcoming xrpld 3.3.0 release, targeting privacy, atomic settlement, and easier institutional onboarding.
Summary
- Five proposed amendments are expected to accompany the xrpld 3.3.0 software release.
- Confidential MPT would support private token balances and transfer amounts using cryptographic proofs.
- Batch transactions would enable delivery-versus-payment and atomic settlement across multiple accounts.
- Amendments require validator approval before they can activate on the XRP Ledger.
XRP Ledger v3.3.0 targets institutional transactions
Jazzi Cooper, head of product at RippleX, outlined the proposed changes in a post on X. The xrpld 3.3.0 release is anticipated next week, although releasing the software will not immediately activate its amendments.
“XRPL has already proven it can support tokenized assets at scale. Now it’s time to put these assets to use: global transfers, trading, collateralizing, and settling,” Cooper said.
She added that the five amendments would move the network closer to supporting those activities. The proposals cover confidential token transactions, transaction batching, delegated permissions, sponsored costs, and adjustable token properties.
Each amendment must pass through the XRP Ledger’s validator-governed approval process. Amendments affecting transaction processing generally need at least 80% support from trusted validators for two consecutive weeks before taking effect.
The upgrade follows the activation of fixCleanup3_2_0 on July 29. XRPScan data showed that the amendment received support from 30 of 35 participating trusted validators, equivalent to 85.71%.
Its activation made version 3.2.0 the minimum software release compatible with the updated mainnet rules. Nodes running version 3.1.0 or earlier became amendment-blocked and could no longer follow validated ledgers correctly.
Confidential MPT would add token privacy
Confidential MPT would add native privacy features for Multi-Purpose Tokens on XRPL. The proposal uses elliptic-curve encryption and zero-knowledge proofs to conceal token balances and transfer amounts while allowing authorized verification.
Issuers and holders could keep transaction data private from the public while granting access to a designated third party, such as an auditor or regulator. The arrangement is intended to balance commercial confidentiality with institutional reporting and compliance requirements.
“For financial institutions, privacy is often a prerequisite for using public blockchain infrastructure,” Cooper said.
The proposal could be relevant to US-regulated institutions evaluating public blockchains for tokenized assets. Banks, broker-dealers and asset managers often need transaction confidentiality while retaining records that can be reviewed by auditors or regulators.
However, the amendment would represent a network-level technical function, not regulatory approval for any specific financial product or activity.
Batch and delegated permissions support settlement
The proposed Batch amendment would allow transactions involving multiple accounts to execute atomically within one ledger. Either every part of the batch would succeed, or the entire operation would fail.
The structure can support delivery-versus-payment, where the transfer of an asset and its corresponding payment occur together. It could also reduce settlement risk in more complicated workflows involving several accounts or assets.
Permission Delegation would allow an account holder to grant narrowly defined transaction permissions without transferring control of the account’s signing authority. An institution could therefore authorize a treasury or operations team to perform specific tasks while keeping its issuance keys under separate control.
Sponsored Fees and Reserves would address another onboarding issue by allowing a bank, issuer, or platform to cover transaction fees and account reserves for users.
“Users continue to own their accounts and keys, while removing one of the biggest onboarding hurdles: requiring every participant to acquire and manage XRP before they can interact with the network,” Cooper said.
Dynamic MPT would make issued tokens adjustable
Dynamic MPT, the fifth proposed amendment, would let issuers modify selected token properties after issuance. Adjustable fields could include transfer fees, metadata, and other predefined features.
Issuers currently may need to create a replacement token when important terms require changes. Dynamic MPT is intended to provide limited flexibility without requiring an entirely new issuance, although the final amendment specifications will determine which properties can be changed.
The proposed features arrive as XRPL records increased tokenized real-world asset activity. RWA.xyz data showed that the network added approximately $2.6 billion in RWA value during the six months through July 26, excluding stablecoins.
That ranked XRPL second among tracked networks for net RWA inflows, behind BNB Chain at about $3 billion and ahead of Stellar at roughly $2.1 billion. XRPL’s combined distributed and represented RWA value reached approximately $4.38 billion.
Validator operators will be able to review the amendments as their specifications become available. Activation will depend on whether each proposal independently secures the required consensus after xrpld 3.3.0 is released.
