XRP Ledger Fix Wins Every Validator Vote, Activates Oct. 9

The next change to the XRP Ledger has the validator set behind it. XRPScan's page for fixBatchV1_2 shows the amendment at 100% consensus, with no trusted validator listed as not voting for it, and gives October 9, 2026 at 2:12 PM UTC as the earliest moment it can switch on.

That is a wide margin. An amendment needs more than 80% support held for 14 days to activate, and with 35 votes in play the bar works out to 29. This one cleared it with room to spare.

What Changes in the Fix

Batch is the ledger's tool for bundling. It lets several transactions ride into one package that gets processed together, which turns a string of separate commitments into a single one.

The first attempt at that feature did not survive contact with mainnet. The original Batch amendment was disabled in version 3.1.1 because of a bug and replaced by BatchV1_1, which is still completing its own activation. fixBatchV1_2 is the narrower cleanup on top: the xrpld 3.4.1 changelog describes it as rejecting Batch inner transactions with the wrong wrapper, alongside integer-arithmetic hardening in the payment engine and ledger helpers.

A Batch carries inner transactions inside it, and each one is expected to arrive in a particular form. If one turns up with the wrong wrapper, the fix rejects it. That is a validation rule rather than a new capability, and small rules like it are usually the ones that close a gap a larger release left open.

The 14-Day Window and the 80% Floor

This is the part that keeps a near-unanimous vote from being a formality.

XRPScan's timestamps put fixBatchV1_2's majority period starting September 25, 2026 at 2:12 PM UTC. That makes October 9, 2026 at 2:12 PM UTC the earliest possible activation, not a guaranteed one. Support has to stay above 80% the whole way. One slip to 80% or lower rejects the amendment and restarts the 14-day timer from zero.

Votes are counted every 256 ledgers. At the time of reading, XRPScan showed the network at ledger 107,474,295, with the next count due at 107,474,432.

Two More Amendments in the Same Queue

fixBatchV1_2 is not travelling alone. XRPScan's amendments list shows three amendments inside their 14-day activation periods, all counting down within two days of each other: fixBatchV1_2, BatchV1_1 and PermissionDelegationV1_1.

BatchV1_1's majority period began September 25 at 2:46 PM UTC, 34 minutes after the fix, so its earliest activation falls on October 9 at 2:46 PM UTC. xrpl.org's known amendments page lists both BatchV1_1 and fixBatchV1_2 as expected on October 9, and PermissionDelegationV1_1 a day earlier, on October 8.

That queue says something about how the ledger moves. The same list also shows 9 amendments still gathering votes, 94 already activated and 7 deprecated, so the three now counting down are the leading edge of a much longer backlog.

What Still Isn't Public

fixBatchV1_2 arrived inside xrpld 3.4.1, which the release notes call an emergency release fixing security-sensitive issues in the XRPL protocol. The amendment shipped with its default vote set to Yes, so validators did not need to opt in manually.

Because the fix is security-sensitive, the source code for 3.4.1 had not been published at release, and developers say a detailed technical report will follow once the amendment activates. Until that report lands, the public account of the defect runs to the changelog line about wrong wrappers, and no more detail has been released.

The same release note says servers not running 3.4.1 will become amendment blocked.

For now the number to watch is the timestamp: October 9, 2026 at 2:12 PM UTC on XRPScan, and whether support stays above 80% until the ledger crosses it.