The XRPL Dashboard recorded 30 yes votes among the 35 trusted validators it tracks when checked at 04:43 UTC on September 26. That count starts a new approval window for the BatchV1_1 amendment — it does not, by itself, complete the activation process.

Key takeaways:

• BatchV1_1 regained 30 of 35 validator votes.
• The previous two-week approval clock has reset.
• At least 29 votes must now hold.
• October 9 is an earliest, conditional date.
• On-ledger activation confirms the upgrade.

The date reset even though the vote count recovered

BatchV1_1 reached 30 supporting validators on September 15. Under the original timetable, that placed activation near September 29. The majority was then removed on September 25 and re-formed later that day, moving the estimate about 10 days later.

The dashboard identifies the flag ledgers at which the earlier majority was removed and the new one was recorded. It does not disclose why the temporary change occurred or identify an individual validator's reasoning. The confirmed development is the reset itself: an amendment needs uninterrupted backing through the full window, even when its vote count later returns to the same level.

That makes October 9 a conditional estimate derived from the ledger's current majority record. It can move again before activation.

Thirty yes votes leave one vote above the line

XRPL's threshold is often shortened to "80% support," but the rule is stricter: an amendment needs more than 80% backing from trusted validators. With 35 validators in the dashboard's monitored set, 28 votes equal exactly 80%. BatchV1_1 needs 29 yes votes to start or preserve its majority.

The present tally of 30 equals roughly 85.7%. It has one vote above the 29-vote requirement. A move from 30 to 29 would leave the countdown intact; a move to 28 would trigger another reset at the relevant flag ledger.

The XRPL amendment process checks votes around flag ledgers, typically about every 15 minutes. These flag ledgers act as recurring checkpoints where support is measured, and the two-week clock only runs while the tally stays above the threshold. Once an amendment has held more than 80% support for two weeks, the change applies permanently to subsequent ledger versions.

Server code and Mainnet rules are separate stages

Coindoo previously explained how BatchV1_1 can coordinate connected payment instructions. That utility is not the issue raised by the reset. The current question is whether the corrected amendment can complete the validator process required for those transaction rules to take effect on Mainnet.

Availability in server software makes an amendment eligible for validator voting, while Mainnet behaviour changes only after the network enables it. This separation is why a dashboard date should be read as a live estimate of governance progress rather than a product-release announcement.

Why the earlier security withdrawal matters now

BatchV1_1 is the corrected successor to an earlier Batch amendment that was withdrawn before Mainnet activation after researchers found an authorization flaw. The original version never became active, and the issue therefore did not expose Mainnet user funds.

According to the XRPL vulnerability disclosure, the replacement added changes to the signing and authorization checks and underwent further review before returning to voting. The episode shows how the process works as designed: code that becomes available in server software can still be stopped before it ever changes Mainnet rules. The fresh 14-day window is the current governance test for that revised implementation.

The confirmation to watch is on the ledger

October 9 matters only if the majority remains in place through the full window. The confirmation will come from an EnableAmendment pseudo-transaction recorded by the ledger, after which BatchV1_1 becomes an active Mainnet rule for subsequent ledgers.

Until that event appears, the relevant update is the continuity of the validator majority. The dashboard provides a useful view of the current countdown, but the ledger's activation record will determine whether the corrected Batch amendment has actually crossed the line into live XRPL infrastructure.

This article is provided for informational purposes only and does not constitute financial or investment advice. Validator support and amendment status can change.