PUMP Price Surges 15% as Whales Accumulate $3.58M 
Kraken Parent Payward Adds 24/7 Settlement With Singapore Gulf Bank 
SEC Investor Reform Validates Barry Silbert’s Tokenization Vision 
Sector Spotlight: Data Availability and Storage Lead 24-Hour Market Gains 
Bitcoin Outflows From Binance Hit Three-Year High as Whales Accumulate 
Strategy’s STRC Nears $100, Raising Prospects for Major Bitcoin Buys 
Becton Dickinson to Invest $3 Billion in U.S. Medical Manufacturing 
Ripple Expands Brevan Howard Deal With Prime Brokerage Services 
China Shuts 670 Banks as Bitcoin Eyes Financial Risks 
Zcash Prepares for NU7 Upgrade as Zebra Gets Key Security Fixes 
BofA Raises Coinbase Stock Target to $203 on Stablecoin Growth 
Stellar Leads RWA Tokenization Growth With $36.4M Inflow 
Weekly Crypto Pulse: $528M ETF Inflows Meet a Cooling US Economy 
Huawei, Qualcomm Sign Multi-Year AI and 5G Patent Deal 
Peter Brandt Flags Key XRP Breakout at $1.6572 
Add as a preferred source on Google
The XRP Ledger is preparing for a significant network upgrade, with Batch V1.1 scheduled to activate on the XRPL mainnet on October 9, 2026.
According to XRPScan data, Batch V1.1 is a replacement amendment introducing the corrected Batch implementation included in xrpld v3.3.0. The amendment is expected to activate alongside fixBatchV1_2 after its activation timer was reset.
Batch had previously secured the required validator majority and was scheduled to go live on September 29. However, the timeline changed after developers identified a minor issue involving the fix included in the xrpld 3.4.1 release. XRP Ledger validators subsequently changed their votes, temporarily rejecting the amendment so that the two-week activation period could restart and Batch could launch together with its fix.
Under the XRPL consensus system, amendments must maintain support from more than 80% of trusted validators for two consecutive weeks before activation. If support falls below that threshold, the amendment is temporarily rejected and the countdown begins again.
Batch, also known as XLS-56, is designed to allow multiple XRP Ledger transactions involving different accounts to execute atomically within a single ledger close. In its all-or-nothing mode, the failure of one transaction causes the entire batch to be rolled back.
The functionality could become important for institutional and developer applications requiring coordinated transactions. Batch is expected to support or accelerate XRPL use cases already under contract or development, including atomic multi-party settlements.
Another XRP Ledger upgrade is approaching even sooner. The Permission Delegation amendment is expected to reach the mainnet on October 8, one day before Batch.
RippleX has highlighted transaction batching as part of broader efforts to prepare XRPL for increasingly complex financial activity. At the recent XRP Seoul event, RippleX engineering head JA Akinyele discussed upgrades involving formal verification, adversarial testing and structural improvements aimed at supporting developers, institutions and users.
If validator support remains above the required threshold, Batch V1.1 will mark another major step in expanding XRP Ledger functionality.
