BTC $82,917 
ETH $2,656 
USDT $0.9997 
BNB $761.92 
XRP $1.49 
USDC $0.9998 
SOL $118.57 
TRX $0.3343 
ZEC $1,558 
FIGR_HELOC $1.06XRP batch upgrade gets fix in xrpld 3.4.1 as community resets vote
The XRP Ledger Batch amendment and its fix now head toward the same activation date after validators reset the vote.
The short answer
XRPL developers released xrpld 3.4.1, which adds the fixBatchV1_2 amendment for the Batch feature. Validators and Ripple flipped votes from Yes to Nay to reset the Batch vote so the amendment and its fix can activate together. The fix holds 94.29% consensus on XRPScan data, and Batch is now expected to activate on October 9, 2026.
What happened
XRPL developers released xrpld 3.4.1, a software version that adds a fix for the Batch feature and broader stability improvements. Validators and node operators were encouraged to upgrade as soon as possible.
The release introduces the fixBatchV1_2 amendment, which addresses a minor issue affecting Batch and does not put user funds at risk. The amendment is marked as Default Yes, so it needs no manual voting, and it holds 94.29% consensus according to XRPScan data.
The activation timer for the amendment reset after a coordinated effort by the validator community. Hussein Zangana (Vet) said he and Ripple, working with the XRP community, changed votes from Yes to Nay just enough to reset the vote on the Batch amendment, so the fix and Batch could activate together.
Developers said there was no impact on the mainnet and no loss of funds. The release notes do not report stolen XRP or a live mainnet attack.
Why it matters
Batch (XLS-56) lets transactions from several accounts run atomically inside one ledger close. It will let users group up to eight inner transactions into one transaction, where every step succeeds or the whole batch fails. That design may help tokenized asset settlement.
Amendments need support from more than 80% of trusted validators for two weeks before they are enabled. If support drops below that level, the amendment is temporarily rejected and the two-week period restarts. Servers that miss xrpld 3.4.1 before activation could become amendment-blocked and lose sync with the wider network.
The security fix remains private. XRPL said it will publish the source code later, along with a report explaining the issue, and described the update as preventive.
What the data shows
The fixBatchV1_2 amendment is marked Default Yes and sits at 94.29% consensus on XRPScan data. BatchV1_1 regained support from 30 of 35 trusted validators, above the 29 votes now required.
Batch is expected to activate on October 9, 2026, in the next 13 days, with activation possible around 14:46 UTC. The permission delegation amendment is expected in the next 12 days, on October 8, 2026.
Background
Batch (XLS-56) had earlier gained majority support and was set to activate on September 29, 2026. Validator support briefly fell below 80% on Sept. 25, which reset the approval period.
The current BatchV1_1 version replaced an earlier Batch proposal that developers withdrew after finding a serious signature-checking problem before activation.
What is still unclear
- The nature of the security issue behind the release is not public. The security fix remains private, and developers and operators still have only limited public detail on the flaw.
- When the source code and the technical report will be published is not stated in the reports.
What to watch
- 2026-10-09 Batch and fixBatchV1_2 are expected to activate together, with developers saying the fix could activate if voting stays above the required level.
Questions readers ask
What is xrpld 3.4.1?
It is the latest XRPL software release, which includes a fix for the Batch feature and broader stability improvements. Validators and node operators were encouraged to upgrade as soon as possible.
What does the XRP Ledger Batch amendment do?
Batch (XLS-56) lets transactions from multiple accounts execute atomically in a single ledger close. It will let users group up to eight inner transactions into one transaction, where every step succeeds or the whole batch fails.
When will Batch activate on the XRP Ledger?
Batch is now expected to activate on October 9, 2026, the same day as the fixBatchV1_2 amendment, according to XRPScan data. Developers said the fix could activate that day if voting stays above the required level.
Why did the Batch vote reset?
Hussein Zangana (Vet) said he and Ripple, in coordination with the XRP community, flipped votes from Yes to Nay just enough to reset the vote on the Batch amendment. The reset was needed so the amendment and its fix could activate at the same time.
