TLDR
- XRPL released version 3.4.1 to fix security-sensitive protocol issues.
- The update introduces fixBatchV1_2, with validators voting “Yes” by default.
- BatchV1_1 activation was delayed after validator support briefly fell below 80%.
- Both BatchV1_1 and fixBatchV1_2 could activate on Oct. 9 if support holds.
- Server operators must upgrade before activation or risk becoming amendment-blocked.
XRPL developers released xrpld 3.4.1 after finding security-sensitive protocol issues tied to the XRP Ledger Batch upgrade. They urged server operators to install the update before the next activation window closes.
The update adds fixBatchV1_2 and sets the default validator vote to Yes. Developers said the fix has gained supermajority support and could activate on Oct. 9 if voting stays above the required level.
Validators Face Oct. 9 Deadline
The timing follows a delay to BatchV1_1. The amendment had been on track for Sept. 29, but validator support briefly fell below 80% on Sept. 25. That reset the two-week approval period.
BatchV1_1 later regained support from 30 of 35 trusted validators, above the 29 votes now required. The change means activation could occur around 14:46 UTC on Oct. 9, matching recent XRP market coverage.
The security fix remains private. XRPL said it will publish the source code later, along with a report explaining the issue. Developers and operators still have only limited public detail on the flaw.
The release notes do not report stolen XRP or a live mainnet attack. XRPL described the update as preventive. The version also rejects Batch inner transactions that use the wrong wrapper and strengthens integer checks in payment and ledger code.
XRP Ledger Batch Upgrade Moves With Fix
Batch will let users group up to eight inner transactions into one transaction. It can support atomic execution, where every step succeeds, or the whole batch fails. That design may help tokenized asset settlement, including payment and asset transfers in one operation.
The current BatchV1_1 version replaced an earlier Batch proposal that developers withdrew after finding a serious signature-checking problem before activation. The latest reset allows BatchV1_1 and fixBatchV1_2 to move together, while stablecoin rule proposals keep digital asset controls in focus.
Servers that miss xrpld 3.4.1 before activation could become amendment-blocked. They may then lose sync with the wider network and fail to follow the validated ledger.
A separate PermissionDelegationV1_1 amendment also had its approval period reset. It could activate as early as Oct. 8 if validator support holds. The upgrade calendar now places XRPL operators under close timing pressure, alongside wider crypto guidance issued during the past week.
Be the first to comment