Rewrite the following content into a 2000-word, SEO-optimized article in English. Write it in the style of a professional journalist or news reporter. The article should be fully humanized, natural, and engaging — not robotic or repetitive.
Focus on clarity, flow, and storytelling while preserving the meaning of the original. Structure the article into 6 well-developed paragraphs with smooth transitions, strong headlines, and a professional tone. Use varied vocabulary, sentence lengths, and natural phrasing to make it read like human-written journalism.
Avoid keyword stuffing, but naturally integrate important SEO keywords throughout the article. Ensure the final article feels like it was written by a skilled reporter for a reputable news outlet.
In a recent development, a new XRPL software version, xrpld 3.4.1, has been released, which includes a fix for the batch feature. The activation timer for the long-awaited amendment also reset after a coordinated effort by the validator community.
According to $XRP Ledger operations, the latest xrpl software release, xrpld 3.4.1, includes a Batch fix and broader stability improvements. Validators and node operators have been encouraged to upgrade as soon as possible.
While there were no additional details on the nature of the issue, developers say that there has been no impact on the mainnet and no loss of funds.
The new xrpld 3.4.1 release introduces the fixBatchV1_2 amendment, which addresses a minor issue affecting Batch and does not pose a risk to user funds.
The fixBatchV1_2 amendment is marked as Default Yes, implying it has no need for manual voting and is currently at 94.29% consensus according to XRPScan data. Both Batch and the fix amendment are now in the activation period, with a detailed technical report expected afterward.
What happened?
Hussein Zangana (Vet) gives a glimpse of what happened behind the scenes, noting that 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. This was necessary for the activation of the Batch amendment and its fix to occur at the same time.
MAN you guys have no idea how proud i’m of the $XRP Ledger Validator Community, RippleX and XRPLF!
Me and Ripple flipped votes from Yes to Nay (in coordination with the community) just enough to reset the vote on Batch and allow the fix and Batch to go in together.
Batch is a… https://t.co/NodsRRIPVz
— Vet (@Vet_X0) September 25, 2026
In line with XRPL’s consensus process, amendments must maintain two weeks of support from more than 80% of trusted validators to be enabled. If support drops below 80%, the amendment is temporarily rejected, and the two-week period restarts. Amendments can gain and lose a majority any number of times before they become permanently enabled.
Batch (XLS-56), which allows multiple XRPL transactions from multiple accounts to be executed atomically in a single ledger close, had earlier gained majority and was set to activate on September 29, 2026. This timing shifted after the amendment was temporarily rejected to restart the two-week activation window.
According to XRPScan data, Batch is now expected to activate in the next 13 days, on October 9, 2026, the same day as the fixBatchV1_2 amendment.
The permission delegation amendment also had its activation timer reset after it briefly dropped below 80% support and is now expected to arrive on the mainnet in the next 12 days, on October 8, 2026.
