XRPL Lists BatchV1_1 as Expected September 29, 2026, Not Yet Enabled
XRPL Lists BatchV1_1 as Expected September 29, 2026, Not Yet Enabled The XRP Ledger's official Known Amendments record lists BatchV1_1 as expected on Septemb...
XRPL Lists BatchV1_1 as Expected September 29, 2026, Not Yet Enabled
The XRP Ledger's official Known Amendments record lists BatchV1_1 as expected on September 29, 2026, a successor to the withdrawn Batch amendment, but the feature is not enabled on mainnet.
Batch transactions would let XRPL users group multiple operations into one atomic package. That design is associated with the XLS-56 specification. For readers tracking protocol status, the official record still matters more than the design: BatchV1_1 has an expected amendment date, and it is not enabled on mainnet.
Who, What, When, Where: Breaking Down BatchV1_1
BatchV1_1 targets the XRP Ledger, or XRPL, the decentralized network powering XRP. This amendment aims to introduce batch transactions, allowing users to group operations like payments or account sets into one atomic unit. It builds directly on the XLS-56 design for batch transactions.
The 'when' centers on September 29, 2026, listed as the expected date on XRPL's authoritative source. This is not activation: it's a projected timeline based on current network consensus trends. The 'where' is straightforward, the mainnet XRPL, maintained by validators worldwide through the standard amendment process.
Confirmed Evidence from the Official Record
The evidence starts with the XRPL Known Amendments page, the definitive ledger for amendment status. There, BatchV1_1 appears with these specifics:
- Introduced in xrpld version 3.3.0.
- Status: Expected, dated 2026-09-29.
- Amendment ID: 9F287AED3CDB50A7BD1ACEC24296A30C9B5230CCD136219317AC790E3B884377.
- Default vote: No.
This listing confirms BatchV1_1 has advanced to 'Expected' status, meaning it has held majority support long enough to project enablement. No third-party scanners or vote tallies override this: the Known Amendments page is the source of record for blockchain professionals.
Context and Timeline of XRPL Amendments and BatchV1_1
XRPL amendments evolve the protocol through a deliberate, decentralized process. As detailed in the official amendments documentation, proposals require over 80% validator support for two continuous weeks to activate. An 'Expected' label signals strong, sustained backing, but it sets only a tentative date.
BatchV1_1 is the successor to the original Batch amendment. The earlier version was removed in xrpld 3.1.1 because of a bug. BatchV1_1 was introduced in 3.3.0.
If BatchV1_1 enables, it would add atomic batching of multiple operations. That outcome still depends on validator support holding through the expected window. An expected date is not a guarantee of enablement.
Unknowns and Disputed Points Around the Expected Amendment Date
Clarity comes with caveats. The September 29, 2026, expected date for BatchV1_1 could shift if validator support dips below majority at any point. Amendments live or die by ongoing consensus; a single week's wobble resets the clock.
Disputes often swirl around unofficial vote trackers, like those on explorer sites, which lag or misreport real-time validator stances. Some claims suggest batch features are already live: those stem from testnets or unrelated code, not mainnet reality. Developers know the rule: check the Known Amendments page first, always.
Technical details beyond the amendment ID remain light in public records. While XLS-56 outlines the spec, full implementation quirks await enablement.
What to Watch Next for XRPL Amendments
Keep eyes on the Known Amendments page for status shifts: from Expected to Enabled, or potential delays. Monitor xrpld release notes for testing updates. Validator announcements and cluster maps offer indirect signals on consensus health. For BatchV1_1, integration guides and dev tools will emerge closer to the date, if it holds.
Broader XRPL amendment activity, like lending protocols in recent releases, provides ecosystem context without overshadowing this milestone.
Sources
- XRPL Known Amendments (source of record for BatchV1_1 status and expected date).
- XRPL Amendments Process Documentation.
- XLS-0056 Atomic/Batch Transactions Specification.
This CryptoWorkPro article is informational editorial coverage based on the cited, dated Known Amendments record listing BatchV1_1 as expected on September 29, 2026. This article is not financial, legal, or investment advice. An expected date is not enablement; check the official Known Amendments page and XRPL documentation before any protocol or implementation decision.