The XRPL Dashboard recorded 30 yes votes among its 35 tracked trusted validators when checked at 04:43 UTC on September […]
The post XRP Ledger’s Batch Upgrade Regains Votes: Why Oct. 9 Is Still Conditional appeared first on Coindoo.
The XRPL Dashboard recorded 30 yes votes among its 35 tracked trusted validators when checked at 04:43 UTC on September 26. The amendment has cleared the first voting condition; it still must keep that support long enough to activate.
Key Takeaways
- BatchV1_1 has 30 supporting validators.
- The earlier two-week countdown ended.
- Twenty-nine votes preserve the new clock.
- October 9 remains an earliest date.
- An on-ledger record confirms activation.
Thirty votes leave only a one-vote buffer
XRPL’s threshold is often described as “80% support,” but the rule requires more than 80%. With 35 validators in the dashboard’s monitored set, 28 votes equal exactly 80%. BatchV1_1 therefore needs 29 votes to start and preserve its majority.
Thirty votes amount to roughly 85.7%, leaving one vote of room. A fall from 30 to 29 would keep the current approval period alive. A fall to 28 would end it at the relevant flag ledger and force another two-week wait after support returned.
The XRPL amendment process checks validator support around flag ledgers, typically about every 15 minutes. This is why the figure on the dashboard is useful, but not a launch confirmation.
The first countdown did not pause; it ended
BatchV1_1 first reached 30 supporting validators on September 15, placing activation near September 29 if that backing had remained intact. The tracker then recorded the majority as lost on September 25 before it returned later that day.
That sequence did not put the original clock on hold. It ended the first window and began a completely new one, pushing the earliest projected date by about 10 days. The dashboard identifies the flag ledgers where those status changes occurred, but does not state why the temporary vote change happened or attribute it to any particular validator.
That distinction is central to the story. October 9 is derived from the current uninterrupted-majority record. It can change again before the amendment becomes active.
Code release and Mainnet activation are different events
Coindoo previously explained how BatchV1_1 could coordinate connected payment instructions. That potential utility does not mean the feature is already live. Inclusion in server software makes an amendment available for validators to support; Mainnet rules change only after the network finishes the amendment process.
For users and developers, the practical takeaway is simple: the dashboard date is a governance countdown, not a product-release announcement.
Why the withdrawn version is still relevant
BatchV1_1 replaces an earlier Batch amendment that was withdrawn before Mainnet activation after researchers identified an authorization flaw. The original version never became active, so the issue did not expose Mainnet user funds.
The dashboard does not link the September 25 vote reset to a fresh technical problem. The earlier security history matters because this is the corrected amendment now moving through the approval process. In its vulnerability disclosure, XRPL said the replacement added changes to signing and authorization checks and underwent additional review before returning to validator voting.
What to watch before October 9
- The validator tally: 29 votes or more preserves the current countdown; 28 would reset it.
- The projected date: the dashboard should continue to show October 9 as the estimate while the majority holds.
- The ledger record: an
EnableAmendmentpseudo-transaction is the confirmation that BatchV1_1 has become an active Mainnet rule.
The key development is no longer that BatchV1_1 has regained 30 votes. It is whether those votes remain in place without another interruption. Only that continuity can turn a projected date into an activated XRPL amendment.
This article is provided for informational purposes only and does not constitute financial or investment advice. Validator support and amendment status can change.
The post XRP Ledger’s Batch Upgrade Regains Votes: Why Oct. 9 Is Still Conditional appeared first on Coindoo.
Source: https://coindoo.com/xrp-ledgers-batch-upgrade-regains-votes-why-oct-9-is-still-conditional/
More Crypto News
Check our Market Overview
Disclaimer: This article is for informational purposes only and does not constitute financial advice. Always conduct your own research (DYOR).
