XRP Ledger plans to implement batch amendment updates following the bug report

Developers of the XRP Ledger (XRPL) have signaled their next steps following the discovery of a serious bug through the Bug Bounty program.

In a recent post on X, validator Vet summarized the developments related to batch amendment and what the community can expect in the near future.

On February 20, the XRP Ledger Foundation announced that they had received a bug report related to batch amendment through the Bug Bounty program. The organization emphasized that XRPL is not affected by the bug and the network remains secure. While reviewing the report submitted by the community, the XRP Ledger Foundation called on validators to vote veto against the batch amendment.

Vet stated:

Although no specific timeline has been set, Vet believes that the reasonable next steps may include:

In the latest update on X, the XRP Ledger Foundation said that the fix is being finalized and undergoing additional validation steps before being integrated into the new software update. At the same time, the organization is preparing to release an official version to remove the current batch amendment, reaffirming that XRP Ledger remains unaffected and continues to operate securely.

Bug in batch amendment

According to earlier information, the bug was discovered just before the batch amendment reached enough votes to be activated. Batch transaction proposals allow for atomic execution of multiple transactions simultaneously, making it easier for developers to build applications capable of generating revenue directly on-chain.

This has been a long-awaited upgrade by the community, as it enables the deployment of paid features, automation of processes, and development of applications with revenue models integrated directly on the blockchain.

Additionally, another bug was found in an amendment called fixbatchinnersigs — designed to fix the issue where internal transactions within a batch transaction are flagged as having valid signatures.

In a recent blog post on XRPL, Ripple announced that they have rotated the GPG keys used to sign rippled packages.

Users are advised to download and trust the new keys to avoid issues during upcoming upgrades, as the automatic upgrade process may not work if the new keys are not verified. XRPL users need to add Ripple’s GPG key to sign packages and verify the fingerprint of the newly added key to ensure a smooth update process.