XRP Ledger moves Batch activation to October 9 after emergency 3.4.1 release
Ripple says asset managers are preparing to use XRP Ledger Batch, but an emergency 3.4.1 release moved the expected activation from September 29 to October 9.
Why it matters
Institutional use of Batch is described as prospective rather than live, since RippleX has not named a production asset manager with a mainnet Batch transaction. The date shift means activation depends on validator support for fixBatchV1_2 rather than a fixed September 29 date.
Where the sources disagree
Expected XRP Ledger Batch activation date
September 29 activation expectation
Crypto.News
October 9 activation via fixBatchV1_2, contingent on validator support
Crypto.News
Crypto.News reports the expectation moved from a September 29 activation to an October 9 amendment, with the later date still conditional on validator support for fixBatchV1_2.
Key facts
Ripple says asset managers are preparing to use XRP Ledger Batch.
Reported by Crypto.News
XRP Ledger 3.4.1 shipped a security-sensitive Batch fix on September 25 as an emergency update.
Reported by Crypto.News
The expected Batch activation moved from September 29 to an October 9 amendment called fixBatchV1_2.
Disputed figureReported by Crypto.News
The Foundation expects fixBatchV1_2 to enable on October 9 only if validator support persists.
Reported by Crypto.News
A successful outer Batch can mask failed inner transactions unless the application checks their results.
Reported by Crypto.News
RippleX has described asset managers and commercial projects preparing for Batch without publicly naming a production asset manager with a live mainnet Batch transaction.
Reported by Crypto.News
What happened
Crypto.News reports that Ripple says asset managers are preparing to use XRP Ledger Batch, a transaction type that lets several ledger actions settle or fail together. An emergency security release, XRP Ledger 3.4.1 on September 25, shifted the expected activation from September 29 to an October 9 amendment the Foundation calls fixBatchV1_2, which it expects to activate only if validator support holds. Under the published specification a Batch holds between 2 and 8 inner transactions, and four modes decide whether all, one, a leading prefix, or any qualifying inner transaction executes. Crypto.News notes that RippleX has described asset managers and commercial projects getting ready for the feature but has not publicly named a production asset manager running a live mainnet Batch transaction. The same report flags that a successful outer Batch can hide failed inner transactions unless the application checks each result.
How the story developed
- Update
XRP Ledger 3.4.1 emergency release carries a Batch security fix
The XRPL Foundation release notice calls version 3.4.1 an emergency update for a security-sensitive Batch issue.
- Update
September 29 activation expectation dropped before the date arrived
The Batch date moved to October 9 after the emergency release, according to Crypto.News.
- First report
First report by Crypto.News
Asset managers are preparing for XRPL Batch. What can it actually do?
- Update
Crypto.News reports Ripple's claim on asset manager preparation
The report says Ripple describes asset managers as preparing to use Batch, with no named production asset manager on mainnet.
- Update
fixBatchV1_2 amendment targeted for October 9 if validator support holds
A scheduled date reported by the Foundation, not a completed activation.
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| Crypto.News Crypto media | Asset managers are preparing for XRPL Batch. What can it actually do? | Original |