XRPL Validators Set to Vote on Upgrade Adding Batch Transactions and Confidential Transfers

What is in the amendment package

The package is expected to include batch transactions, confidential transfers, sponsored fees and reserves, permission delegation, dynamic Multi-Purpose Tokens, and a bundled fix for an unspecified bug. Vet also said the release contains significant performance optimizations designed to make nodes run more efficiently and improve overall network reliability.

Some of the proposed additions would change how transactions are handled on the ledger. Batch transactions would let multiple transactions be grouped together. Confidential transfers, if approved, would hide transaction amounts while preserving the integrity of the ledger. Sponsored Fees and Reserves, identified in the article as XLS-68, would allow third parties to pay transaction fees and reserve requirements on behalf of users.

Development resumed after security work

The expected validator vote follows a period in which other work had reportedly been delayed. Vet said security-related initiatives had put feature development on hold, but that development could now resume. He described the upcoming release as a mix of performance improvements, new functionality and fixes.

The source article did not say when any of the amendments might be activated if they pass, only that validator voting is expected to begin in roughly two weeks.

Reserve requirements become a separate flashpoint

Alongside the software package, a wider governance discussion has emerged over whether XRPL reserve requirements should be reduced again. Vet said he opposes lowering reserves under current conditions, even though he supported earlier cuts.

The article traced the reserve requirement back to an earlier period when activating an account required 1,000 XRP under the so-called create fee era. It said co-founder Jed McCaleb reduced that requirement to 200 XRP in 2013, and that validators lowered reserve levels several more times over the years. At present, activating an XRPL account requires a 1 XRP base reserve.

Vet argued that storage and memory remain scarce network resources and said reserves were designed as a protective mechanism against spam and distributed denial-of-service attacks. He also pointed to increased demand for computing infrastructure during the AI boom as part of the current backdrop for that debate.

Why this matters now

The proposed vote brings together several long-awaited XRPL changes in one release, at the same time that the network is debating how much friction should remain in account creation and resource usage. Based on the source report, the near-term milestone is not activation but the start of validator voting on a package that mixes feature expansion with performance and reliability work.