XRP Validators Hold 85.71% Backing for Batch Upgrade Eyed on October 9

Validators Hold 85.71% for Batch

XRP Ledger validators owe the network one more stretch of consistent backing before its biggest transaction-format change of the year goes live: the Batch amendment needs support above 80% for fourteen consecutive days, and the clock runs toward Friday, October 9. As of Saturday, October 3, the ledger's validator dashboard counted 30 of 35 trusted validators, or 85.71%, in favor of BatchV1_1, the corrected implementation of the XLS-56 batch execution standard. The digital asset platform Uphold, which publicized the tally in an X post, put the expected activation on October 9 provided the ratio does not slip. Validators, the entities that review transactions and vote on network changes, reset the countdown entirely if support falls back below the threshold.

Batch changes how work reaches the ledger. Instead of sending transactions one by one, a user can pack as many as eight into a single submission, and the XLS-56 batch execution standard defines four ways to handle the outcome. The ALLORNOTHING mode executes every operation or none of them, which lets a buyer tie a payment to the delivery of a tokenized asset so one leg cannot complete while the other fails. The other three settings run only the first successful operation, stop at the first failure, or process each operation independently. When several accounts take part, every participating wallet address must authorize the group.

The bundling does not waive costs. A merged submission carries the base fee, a management fee and any applicable signature fee, all paid in XRP, the native asset of the ledger behind one of the market's largest altcoins. September transaction records showed failed attempts still incurring fees, so an operation that never executes can still cost XRP.

3.4.1 Patch Sets Operator Deadline

A second amendment riding the same activation window puts the obligation on server operators. The ledger released xrpld 3.4.1 on Friday, September 25, a security-sensitive patch whose companion amendment, fixBatchV1_2, corrects how batched transactions are validated. The October 3 dashboard tally recorded 34 validators in favor of that amendment. If it activates, servers still running older software can lose synchronization with the network, so operators need to confirm the 3.4.1 update before the target date. Neither date is a guarantee: October 9 is the schedule that holds only while support stays above the required level, and the dashboard treats any dip as a restart of the two-week wait.

The push lands against rising usage. Aggregate data compiled on September 2 showed the ledger's daily average transaction count up 21% to 2.4 million between January and July, and a single ledger processed 2,713 transactions in one close, a throughput record distinct from the Batch change itself. Ripple has been building issuance and trading infrastructure for tokenized assets, announcing investments in Zilo and Licuido in August. Tokenization represents funds, bonds or equity wrappers such as xStocks as blockchain tokens that holders can transfer, a field increasingly tangled with DeFi settlement flows, exactly the traffic a batched submission format is built to absorb. The build-out is visible across our XRP Ledger coverage, including the RippleX lead's account of x402 payments on the ledger.

Support Window Closes October 9

For COINOTAG, the two amendments read as one release with two deadlines. The official batch transactions documentation confirms the four execution modes, while the 3.4.1 release notes state the sync risk plainly: an unpatched server falls behind once fixBatchV1_2 activates, around 10:12 a.m. ET on October 9, with BatchV1_1 following near 10:46 a.m. ET. The XRP price has no scheduled event of its own here; the outstanding work belongs to validators, who must hold more than 80% backing through the full two-week window, and to operators, who still have to ship the 3.4.1 upgrade before that clock expires.