XRPL Validators Reset Batch Vote to Align Upgrade With New Fix

In Brief:

• XRPL validators reset the Batch vote, aligning its expected activation with a fix introduced in the latest server software release.
• The xrpld 3.4.1 update addresses a Batch transaction issue, while operators must upgrade to keep their servers synchronized with XRPL.
• PermissionDelegationV1_1 also had its activation timer reset, and all three amendments still depend on sustained support from trusted network validators.

XRP Ledger validators reset the Batch amendment’s activation timer to align the feature with a fix in the new xrpld 3.4.1 release. The change moved Batch’s projected activation from September 29 to October 9, the expected date for the fixBatchV1_2 amendment.

Batch would allow users to bundle multiple transactions for processing together. Its earlier voting majority had already started the two-week activation period, while the newly released fix required its own period of validator support.

According to XRP Ledger contributor Hussein Zangana, known as Vet, he coordinated with Ripple and community validators to change enough votes from yes to no. Batch briefly fell below the required support level, which reset its activation timer. Validators could then restore their support while the feature and its fix followed the same schedule.

XRPL amendments must maintain support from more than 80% of trusted validators for two weeks before activation. If support falls below that threshold, the timer restarts when the amendment regains a majority.

Also Read:  Nik Bougalis Returns to XRP Ledger Code With Proposal to Rework Core Data Types

xrpld 3.4.1 Gives Validators a Fix for the Planned Batch Launch

The xrpld 3.4.1 release introduces fixBatchV1_2 with its default vote set to yes. According to the XRP Ledger’s release notes, the amendment rejects Batch inner transactions that use the wrong wrapper. The release also includes changes addressing other security and stability issues.

Developers describe 3.4.1 as an emergency release for security-sensitive protocol issues. They have not published the fix’s source code yet and plan to provide a retrospective later. Consequently, the release notes offer limited detail about the underlying issue.

The XRP Ledger Foundation has urged server operators to install 3.4.1 before the amendment activates. Servers running older software could lose synchronization with the network if fixBatchV1_2 gains final approval on October 9.

Meanwhile, the separate PermissionDelegationV1_1 amendment also briefly lost the support required to keep its activation timer running. Its projected activation moved to October 8, one day before Batch and its fix.

October 9 remains a projected date because validator support must hold above the required threshold throughout the voting period. The reset places Batch and fixBatchV1_2 on the same timetable while server operators prepare for the software change.

Also Read: Shiba Inu Activity Surges 351% as SHIB Defends Key Support