Invest1 publisher3 min readPublished
XRP Ledger's Batch upgrade heads for an Oct. 9 activation with one validator to spare
XRP Ledger's Batch amendment has 30 of 35 trusted validators behind it and a projected Oct. 9 start for bundles of up to eight transactions. Bundles cost more in fees than separate sends, and a security fix due that morning forces server operators to update.
The Investor · Invest desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction
What happened
- Amendments must hold more than 80% of trusted validators for two straight weeks, and any lapse below that majority restarts the countdown.
- BatchV1_1 is a corrected implementation of the XLS-56 grouped-execution standard, replacing an earlier version after a security flaw was discovered.
- Batch has four execution modes: all-or-nothing, first success only, stop at the first failure, and each operation handled independently.
- Server software 3.4.1, released Sept. 25 for security-sensitive issues, introduced fixBatchV1_2, a separate amendment changing how grouped actions are checked.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- constraint A two-validator defection would cost Batch at least two more weeks, because a reset countdown has to run the full two-week majority period again from the start.
- decision Server operators have to be on 3.4.1 before about 10:12 a.m. EDT on Oct. 9 whatever happens to Batch, since the fix has its own validator vote and its own clock.
- cost Users carry the failure risk: an all-or-nothing bundle that fails still pays its XRP fees, so every failed attempt is a cost with no transfer to show for it.
BatchV1_1 clears the bar by one validator. The rule requires more than 80% [4]. Eighty percent of 35 is exactly 28, so the amendment needs 29 of the 35 to stay above the line [1], and the Oct. 3 dashboard showed 30, or 85.71% [2]. If two of its backers withdraw before Oct. 9, support falls to 28 of 35, exactly 80%, and the countdown resets [2]. Uphold said on X that more than 85% of validators backed the upgrade and that it could activate Oct. 9 if support held above the threshold [5].
The other clock belongs to fixBatchV1_2. It is projected to activate at about 10:12 a.m. EDT on Oct. 9, 34 minutes before Batch's own projected time of about 10:46 a.m. [13][3]. Counting back the required two weeks from Oct. 9 gives Sept. 25, the day version 3.4.1 shipped with the fix in it [4]. On that count, validators backed the correction on or about the day it was released. Operators then had roughly a fortnight to install it before older servers stop staying in sync [12].
Batch costs more to use than sending the same transactions one by one. A bundle pays the underlying fees of everything inside it, plus an overhead charge and any signature charges [9]. Its floor is therefore the sum of the separate fees with overhead on top [6]. Fees are paid in XRP [8]. The overhead pays for coordination. In all-or-nothing mode a payment and the asset it buys either both transfer or neither does, and every account in a multi-party exchange has to authorize the whole group [7].
The schedule can still split. Each amendment needs its own majority [13], so the fix can activate on time while Batch slips, or the reverse. If both land, I'd expect all-or-nothing bundles to show up mainly in asset-for-payment trades, where a half-completed exchange costs more than the overhead, because a bundle that fails still pays its fees and moves nothing [10]. The counter-case is the independent mode [6]. Developers may bundle unrelated transactions just to cut the number of submissions, and treat the overhead as the price of convenience. If bundles turn up across ordinary payment flow in the weeks after activation, that view is wrong.
The ordinary flow it would be measured against has grown. Average daily transactions rose 21% to 2.4 million from January through July, according to data summarized Sept. 2 [14]. Ripple announced investments in Zilo and Licuido in August as part of its push into issuing and trading tokenized assets [15]. Bitcoin.com's own example of all-or-nothing use is a buyer paying for a digital asset, with neither transfer taking effect if either step fails [7].
What to watch
- The amendment dashboard before Oct. 9: a fall to 28 of 35 validators for BatchV1_1 resets its two-week count.
- Whether fixBatchV1_2 activates near 10:12 a.m. EDT on Oct. 9 as projected, and how many servers drop out of sync.
- Batch usage after activation: whether bundles cluster in asset-for-payment trades or spread across ordinary payments.