XRP Ledger 3.3.0 brings privacy and batch upgrades

0
15

XRP Ledger developers have released version 3.3.0 of the xrpld software, bringing several new protocol upgrades closer to possible activation on the main network.

However, the release does not mean these features are already live. Each upgrade still needs approval from XRP Ledger validators through the network’s amendment voting process before it can become active.

The new version includes work on several major features, including ConfidentialTransfer, BatchV1_1, Sponsor, and DynamicMPT. These updates are designed to improve privacy, transaction flexibility, user onboarding, and token management.

Privacy and transaction improvements

ConfidentialTransfer is designed to add more privacy for Multi-Purpose Tokens (MPTs). The feature would allow token balances and transfer amounts to be hidden while still allowing authorized parties, such as issuers or auditors, to access information needed for compliance.

Another important upgrade is BatchV1_1, which focuses on atomic transactions. This allows multiple transactions to be grouped together and completed as one operation. If one part fails, the entire batch can fail, helping businesses handle complex settlement processes more safely.

The earlier version of the Batch feature was stopped before launch after developers discovered a security issue. BatchV1_1 was created as a corrected version after additional reviews.

New tools for businesses and users

The Sponsor feature would allow third parties to pay transaction fees or reserve requirements for other users. This could make it easier for applications to bring new users onto the XRP Ledger without requiring them to hold XRP just to cover network costs.

DynamicMPT is aimed at token issuers. It would allow certain token properties to be updated later if those changes were allowed when the token was created. This could help businesses adjust to changing regulations or operational needs.

Together, these upgrades show the XRP Ledger’s continued focus on supporting tokenized assets, financial applications, and business use cases.

Features still require validator approval

While version 3.3.0 provides the necessary software, the upgrades will only become active if they receive enough validator support. XRP Ledger amendments require more than 80% approval from trusted validators for two continuous weeks before activation.

Some reports have described these upgrades as already active, but that is not accurate. The features are currently available in the software release and are waiting for the governance process to complete.

The release also includes other technical improvements and fixes. Some changes mentioned in discussions, such as fixCleanup3_2_0, belong to earlier software versions and are not part of the main 3.3.0 feature package.

For XRP users, the update is mainly a technical milestone. It does not automatically create higher demand for XRP or affect its price. The next important steps will depend on validator adoption, voting results, and whether each amendment successfully reaches activation requirements.

Until then, these upgrades should be viewed as new tools moving through the XRP Ledger approval process rather than fully launched mainnet features.