XRP Ledger Nears BatchV1_1 Upgrade with 68% Validator Support

iconCrypto Economy
Share
This is the logo of the coin.
XRP
$1.37-3.14%
AI summary iconSummary
The XRP Ledger’s BatchV1_1 network upgrade has secured 68% validator support as of early September 2026. Included in software version 3.3.0, the blockchain upgrade needs 80% support over 14 days to activate. At current rates, the network upgrade could launch by month-end. The change lets developers batch up to eight transactions, improving efficiency and expanding XRP use cases.

TL;DR:

  • The technical amendment BatchV1_1 reached approximately 68% support among network validators.
  • The code was integrated into XRP Ledger software version 3.3.0, released on August 6.
  • To be activated, the proposal must exceed 80% favorable votes continuously for a 14-day period.

The decentralized payments network is nearing the deployment of one of its most anticipated technical updates. The BatchV1_1 upgrade recently surpassed 68% validator approval, according to technical community members during the early days of September.

This proposal introduces functional enhancements aimed at streamlining complex operations within the ledger.

Unlike the current transactional model of the XRP Ledger, where every action must be recorded individually, this amendment will allow developers to package up to eight distinct transactions into a single operation. According to the software’s official documentation, this capability reduces the need to develop external infrastructure to orchestrate interdependent instructions.

In this regard, network validator Vet stated that the developer community has long awaited this tool to implement direct billing schemes for services. In his view, the functionality will make it easier for applications to curb third-party “free riding” of resources by linking payments and logical executions within the exact same block.

The BatchV1_1 amendment on the XRP Ledger has reached nearly 68% validator support and is aiming for the 80% threshold

Technical Threshold and the BatchV1_1 Activation Window

The XRP Ledger governance protocol requires any amendment to clear an 80% support threshold among trusted validator nodes. Under the protocol’s consensus rules, once that mark is met, the percentage must be sustained without interruption for two full weeks before going live.

If at any point consensus dips below that level during the countdown, the 14-day timer resets immediately.

The prior iteration of this enhancement, originally titled Batch, was disabled earlier this year following the detection of a critical software bug. As a technical remedy, maintainers developed the BatchV1_1 revision, which was formally distributed in version 3.3.0 of the XRP Ledger client on August 6.

Community analysts note that if the current adoption pace of version 3.3.0 holds and crosses 80% in the coming days, the technical feature could go live on the mainnet before the end of September.

Leveraging this tool, software creators can define direct dependencies between distinct instructions on-ledger. This means a sequence of transfers, trust line authorizations, or asset issuances can execute under strict atomicity constraints: if one fails, none will process.

The next milestone for the network rests on validator telemetry reports over upcoming voting rounds, which will confirm whether technical support reaches the threshold needed to initiate the definitive countdown.

Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.