XRP Ledger 3.3.0 to launch next week with five amendments including revived Batch feature

The XRP Ledger is about to get its most consequential upgrade in months. The xrpld 3.3.0 core server update is scheduled for release during the week of August 3-9, and it packs five amendments that touch everything from transaction privacy to institutional onboarding.

Jazzi Cooper, Head of Product at RippleX, announced the update on July 31, framing it as a leap forward for tokenized asset use cases including global transfers, trading, collateralization, and settlement.

What’s actually in the update

Confidential MPT introduces zero-knowledge proofs to Multi-Purpose Token transactions. Token transfers can now be verified as valid without revealing the underlying amounts or details to everyone on the network.

Batch (BatchV1_1) enables atomic execution of up to eight cross-account transactions. Either every transaction in the batch goes through, or none of them do.

Permission Delegation allows for narrowly scoped signing authority. Rather than handing over full account control, users can delegate specific transaction permissions.

Sponsored Fees and Reserves lets institutions cover XRP transaction fees and reserve requirements on behalf of their users.

Dynamic MPT gives token issuers the ability to adjust token properties after creation. Issuers can modify parameters post-launch, which adds flexibility for compliance changes, evolving regulatory requirements, or simply fixing mistakes.

The Batch amendment’s rocky history

The Batch feature deserves its own section because its path to this release has been anything but smooth. The amendment originally reached the validator voting phase back in February 2026, which should have been a routine step toward activation.

A bug bounty program uncovered a critical signature validation flaw that could have allowed unauthorized transaction executions. The bug was severe enough that Ripple pulled the amendment entirely and disabled it in version 3.1.1. No funds were lost during the incident, as the bug was caught before mainnet activation. The discovery pushed Batch’s timeline back by roughly five months.

The reintroduced version, labeled BatchV1_1, presumably includes the fix for that vulnerability. The version bump signals this isn’t just a re-release of the same code.

Version 3.2.0 arrived in June 2026 with memory optimizations, while versions 3.1.1 through 3.1.3 focused on bug fixes. The 3.3.0 release is the first since then to introduce new functional capabilities rather than maintenance patches.

The activation process and what comes next

None of these amendments go live automatically. Each one requires at least 80% approval from XRPL validators, sustained over two consecutive weeks, before activation. Validators need to upgrade their nodes to 3.3.0, then signal support for each amendment individually.

The Batch amendment already failed once due to a security flaw, and while the fix appears to be in place, validators may be more cautious this time around. Investors should watch validator signaling closely in the weeks following the release, as the 80% threshold will be the real test of whether the XRPL community is aligned on this direction.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.