xrpld 3.4.1 is being released with a Batch fix and stability improvements. We’re asking validators and node operators to upgrade as soon as possible. There has been no impact to mainnet, and no loss of funds. There is also a new fix amendment, fixBatchV1_2, which addresses a minor issue with Batch that does not pose a risk to funds. The amendment is marked as Default Yes. Both Batch and the fix amendment are in the activation period and set to activate in 2 weeks. A detailed technical report will be shared after the fix amendment has been activated.

xrpld: THE MIGRATION The XRP Ledger is migrating from rippled to xrpld. xrpld v3.2.0 introduces the fixCleanup3_2_0 amendment, along with various improvements and fixes. All validators and node operators are encouraged to migrate to xrpld v3.2.0 and review their infrastructure to ensure a smooth transition. Release Notes: Migration Script by @Vet_X0 According to data from @XRPScan and @Bithomp, approximately 18% of nodes are currently running xrpld v3.2.0. We appreciate the efforts of all operators participating in this important network transition. #xrpl# #xrpld#

Our Statement on xrpld 3.4.1 At XRP Kuwait, our journey has always been about infrastructure and purpose. Our purpose is decentralization. We pursue that purpose through independently operated infrastructure and responsible participation in the XRP Ledger. Following the discussion surrounding xrpld 3.4.1, we disagree with the claim that operators coordinating an update is, in itself, proof of centralized control. Coordination is not the same as control. Independent operators can assess a situation, communicate with one another, and reach the same conclusion without giving up their independence. As an independent validator operator, we make our own decisions about the infrastructure we operate, the xrpld version we run, and how our validator votes. That independence also carries a responsibility to assess risks and respond when action is necessary. Working with other operators to protect the XRP Ledger is consistent with that responsibility. For critical xrpld releases, we review the available information, assess the risks, and determine the appropriate response. Our priority is to make informed decisions that support the security and stability of the XRP Ledger. Participating in a coordinated response does not replace our independent judgment. The important question is not simply whether operators agree, but how decisions are made and whether operators can exercise meaningful independent judgment. Agreement alone does not establish centralization, just as the presence of independent operators does not resolve every concern about it. We do not claim that XRPL has no decentralization challenges. Broader independent participation, transparency, and responsible operation must remain priorities. Supporting an important update and critically examining the process are compatible responsibilities. At XRP Kuwait, we remain committed to both, with decentralization as the purpose behind our work. We also extend our sincere thanks to the XRP Ledger Foundation @XRPLF and all operators who contributed to the response for their coordinated efforts to address the vulnerability and protect the XRP Ledger. XRPK - XRPKuwait is, and will always remain, an independent XRPL infrastructure provider committed to decentralization.

XRP Ledger is bringing back two features it had to kill @jazzicoop says xrpld 3.3.0 lands next week with five amendments, including reworked versions of Batch and Permission Delegation. Both were pulled earlier after researchers found bugs that would have let an attacker move funds from accounts they didn't control. No money was ever lost because neither made it to mainnet. Sponsored Fees is the sleeper here, letting banks cover XRP costs so users never have to buy any. $XRP

XRP Ledger developers have disclosed an integer overflow in the payment engine through which one transaction could mint spendable XRP far beyond the total supply. It was patched Sept. 25 in xrpld 3.4.1, and the report says there is no evidence it was exploited.

Ripple Announces 'Big Plans' for XRP Ledger XRP Ledger (@XRP) $XRP is preparing for major performance improvements in 2027, Ripple engineering director Vijay Khanna (@vjkhannaripple) says. "We have big plans for performance improvements lined up for 2027," Khanna noted. The plans come amid criticism of the network's transaction speed. Ripple is also working to reduce the infrastructure demands placed on validators. The latest xrpld 3.3.0 release cut node RAM usage by 13% to 23%. Recent software updates have already reduced validator memory usage. The roadmap includes lending pools, native smart contract capabilities, repo markets and options trading. The changes aim to support larger financial transactions without overwhelming the base network.

XRPL accounts can now delegate specific permissions without sharing primary keys. Custom spending limits are unsupported, and developers warn against delegating PaymentBurn until a fix activates; a flaw can let delegates mint tokens. via @hardeyjumoh

XRPL held $1.34B in tracked stablecoins on Oct. 7, @DefiLlama reports. That balance does not measure $XRP demand. Fees and reserves require XRP; larger demand depends on routing and liquidity inventory. Analysis by @akibablade

XRPL Update 📰 XRP Ledger's Batch amendment (XLS-56), backed by over 85% of validators, is set to activate Oct 9, letting up to 8 transactions settle atomically. Great news for the $XRP community 👏