Key points

  • BatchV1_1 lets users submit as many as eight inner transactions as one batch on the XRP Ledger.
  • The related fixBatchV1_2 amendment activated first, closing a validation gap before BatchV1_1 became usable on mainnet.
  • The feature provides atomic and independent execution options, but activation alone does not establish adoption or transaction volume.

The XRP Ledger has activated BatchV1_1 on its main network, adding a way to submit as many as eight transactions together. The amendment became enabled on October 9 after maintaining the validator support required by the network's amendment process, according to XRP Ledger documentation and the project's public security disclosure.

What batching changes

Batching does not merge transfers into one new asset or remove the rules that apply to each transaction. Instead, one outer Batch transaction carries a set of inner transactions for coordinated processing. The XLS-56 design supports several modes, including all-or-nothing execution, in which every eligible transaction must succeed for the group to be applied, and independent execution, in which the inner transactions can be evaluated separately.

Related reporting: XRP Ledger Batch upgrade slips to October 9

That structure can reduce the operational steps needed for workflows containing multiple ledger actions. Potential uses include delivery-versus-payment settlement, over-the-counter exchanges and NFT swaps, because related actions can be submitted as one package. The capability is a protocol building block rather than a consumer product: applications and institutions still have to design controls, interfaces and transaction logic around it.

A security fix activated first

The activation followed a deliberate delay. During re-verification of earlier security findings, developers found that servers did not enforce the required RawTransaction wrapper for every inner transaction. Different software versions could therefore disagree about whether a specially formed batch was valid, creating a risk that ledger validation could stall on a mixed-version network.

Validator operators withdrew support long enough to reset BatchV1_1's activation clock while a separate amendment, fixBatchV1_2, moved through the same process. XRP Ledger's October 9 disclosure says the fix now rejects any inner transaction that uses a non-canonical wrapper. The fix activated shortly before BatchV1_1, so the feature became available only after the validation gap was closed.

The disclosure says the affected BatchV1_1 code had not been activated on mainnet when the issue was found. It also says no loss of funds, private-key compromise, consensus failure or incorrectly processed mainnet transaction occurred from that flaw. Servers must run xrpld 3.4.1 or newer to remain synchronized now that the amendment is enabled.

What activation does not show

Independent reporting by Crypto.news said XRPScan data showed 30 validators supporting BatchV1_1 and five opposing it around activation. The network's standard amendment process requires more than 80% support for at least two weeks before an amendment can take effect.

Mainnet activation establishes that the protocol rules are available; it does not show how many users or businesses will adopt them. No launch announcement identified a production customer, published batch volume or set a commercial timetable. The practical measure will be whether wallets, exchanges and tokenization platforms integrate the feature without adding failure modes or confusing users about which parts of a grouped operation completed.

For developers, the immediate change is concrete: coordinated transaction groups can now be submitted under live network rules, with the wrapper-validation fix enforced across compatible servers. The sequence also shows the amendment process being used to pause a feature, activate a protective rule and then enable the intended functionality. For the wider market, claims about faster adoption, lower costs or new institutional demand remain unproven until applications publish operating results.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.