XRP Ledger Adds Game-Changing Feature as Major Release Nears

RippleX senior software engineer Mayukha Vadari recently revealed in an X post that the Batch amendment pull request (PR) has officially been merged into the XRP Ledger (XRPL) codebase. This means the feature will be included in the upcoming Rippled release.

👀

Congrats @angell_denis on your first XRPL feature amendment!

For those who don’t know what this is, it shows that the Batch amendment PR has been merged, which means that it’ll be included in the next rippled release. pic.twitter.com/APrlKQfksq

— Mayukha Vadari (@msvadari) May 23, 2025

Vet, an XRPL dUNL validator, also tweeted about the milestone, signaling the excitement in the community. XLS-56 Batch Transactions will allow users to batch transactions using the XLS-56d specification and support all transaction types with a limit of eight. The amendment also supports atomic swaps.

XLS-56 allows smart transaction dependency logic within a set of transactions that it bundles, with Vet highlighting its use cases to range from XRPL project monetization to NFT p2p trading.

As reported this week, RippleX software engineer Mayukha Vadari hinted at a ton of new features coming shortly to XRP Ledger, one of which was batch transactions.

Others include Account Permission Delegation, which is currently being tested on devnet. Multipurpose tokens (MPTs), Credentials, Permissioned Domains and Dynamic NFTs features have been released for voting but have yet to be deployed on mainnet. Smart Escrows is also presently testing on the WASM devnet.

Major release anticipated

The upcoming 2.5.0 release, anticipated in June, is expected to result in significantly lower memory and bandwidth use for node operators.

In an April blog post, RippleX hinted at a custom intrusive pointer that can handle strong and weak pointers. When measuring memory usage on a mainnet validator, this change resulted in 10-15% memory savings. This improvement has been merged and will be included in the upcoming 2.5.0 release.

Two fail-safes were also created to prevent a consensus round from remaining in the “establish” phase indefinitely; they will be included in the 2.5.0 release. Squelching was first proposed a few years ago, but never fully implemented. RippleX aims to include this approach in the upcoming 2.5.0 release.

This week, Schuman Financial’s EURØP became the first MiCA-compliant euro stablecoin on XRP Ledger. USDB, Braza Group’s new USD-backed stablecoin, will also launch on XRP Ledger.

Source