XRPL BatchV1_1 protocol change set for September 29 as validators signal support

Validator approval and activation process

Unlike most traditional software updates, protocol amendments in XRPL require more than developer initiative. To become part of the network’s rules, any new feature must receive support from at least 80% of trusted validators for two consecutive weeks. This decentralization ensures that upgrades reflect consensus among the network’s guiding participants rather than decisions from a single company such as Ripple.

If BatchV1_1 secures this supermajority support continuously over the next weeks, its activation date will remain set for September 29. This process gives the broader XRPL community and ecosystem developers advance notice of the pending upgrade.

Technical details and functionality of BatchV1_1

According to the official XRP Ledger documentation, BatchV1_1 will allow accounts to bundle up to eight separate transactions into a single batch submission. These transactions can be structured so that their execution is interdependent.

A standout feature of this update is atomic execution. This means that either every transaction in a batch succeeds together, or the entire group fails, preventing partial execution that could leave contracts or trades incomplete. This capability paves the way for support of atomic swaps and other complex financial operations consisting of multiple, linked steps.

Mini dictionary: Atomic execution, in blockchain, refers to a process where multiple operations are performed all at once or none at all. If any part of the grouped operation fails, the entire set is rolled back, ensuring consistency and preventing partial, potentially problematic outcomes.

With BatchV1_1, developers can tie multiple XRPL transactions together, ensuring that they all succeed or all revert, which addresses many multi-step transaction use cases such as cross-asset swaps and institutional settlement flows.

Security improvements and previous attempt

BatchV1_1 is the second attempt to bring batch transaction functionality to XRPL. Earlier this year, the original Batch amendment was halted after researchers identified a critical security flaw. The vulnerability could have allowed malicious actors to perform unauthorized transactions from other accounts without owning their private keys.

XRPL developers acted quickly, disabling the vulnerable feature before it reached mainnet activation. The corrected BatchV1_1 amendment addresses these security concerns, and its pending implementation marks the feature’s return after a comprehensive fix.

The return of batch transactions with enhanced safeguards makes the upcoming upgrade a particularly notable event in XRPL’s broader 3.3.0 cycle as the protocol moves deeper into tokenization and institutional settlement capabilities.

Ongoing upgrades and ecosystem development

The BatchV1_1 amendment is part of a larger series of protocol upgrades under XRPL version 3.3.0. The network is simultaneously advancing in areas such as tokenization, institutional settlement, and native lending services.

Work is also ongoing for XRPL Lending v1.1, which is undergoing its own validator approval process. RippleX, the developer-focused arm of Ripple, has pointed to XRP collateral as a potential institutional credit use case, further expanding the network’s reach into financial services.