XRP Ledger has released xrpld 3.4.1, a new software version that fixes an issue tied to the batch feature and includes broader stability improvements. The network’s team urged validators and node operators to upgrade as soon as possible. Developers said the issue did not affect mainnet and did not lead to any loss of funds. The release also introduces the fixBatchV1_2 amendment, which defaults to a yes vote and is currently showing a 94.29% consensus rate. Both the amendment and the batch feature have entered the activation period. Before this, some validators switched their votes from yes to no in order to reset the voting timer for the Batch amendment.

XRP Ledger’s BatchV1_1 amendment has entered its final approval window after securing majority validator support on Sept. 15, according to on-chain amendment status data. If support stays above the required threshold for 14 straight days, the feature can go live as early as Sept. 29 at 14:06 UTC. The amendment would let users bundle up to eight XRPL transactions into a single operation with only two outcomes: all succeed or all fail. RippleX engineering lead Ayo Akinyele said the design is meant to address consistency across linked transactions, with use cases such as delivery-versus-payment settlement, collecting service fees at the same time a customer payment is processed, and synchronized transfer of assets and funds. The proposal follows an earlier version that was withdrawn before activation after a major flaw was found in signature verification in February 2026. Ripple said the revised version went through internal testing, AI-assisted analysis, Sherlock’s security competition, and reviews by Halborn and Common Prefix. Akinyele also said Ripple is working with major asset managers, but no institution was named and no timeline or scale was disclosed.

The XRP Ledger's automated market maker (AMM) amendment has reached 80% validator consensus, triggering the activation window. The feature is not yet live; it requires sustained support during the window. Once active, the native AMM will add a direct DeFi layer to XRPL, though it may differ from other chains in architecture and fee models.

Ripple has recommended withdrawing XLS-38, the cross-chain bridge amendment on the XRP Ledger. The company cited the adoption of cross-chain solutions such as Axelar, weak demand from developers, and high maintenance costs as the reasons behind the suggestion. The news was reported by Crypto.news via Techub News.

Sen. Cynthia Lummis said the latest proposal put forward by Sen. Cortez Masto and prosecutor groups was not the product of any agreement with her and does not do enough to protect software developers. In remarks relayed by a Fox Business crypto reporter on X, Lummis also said the proposal fails to give law enforcement the common-sense tools it needs, while adding that the current situation is not workable and that efforts must continue. Under the latest proposal, the Lummis-Grassley amendment would be removed. That amendment had stated that software developers could face criminal liability only if they acted with specific intent to assist money laundering. The update points to an ongoing disagreement over how legislation should draw the line between developer activity and criminal exposure, while also addressing enforcement needs.