XRP Validator Vet Reveals What Comes Next as Batch Amendment Bug Delays Activation

• Batch amendment halted after bug detected before majority vote
• Vet outlines next XRP software update and deprecation
• Foundation confirms network safety as fix undergoes validation

XRP Ledger validator Vet has outlined the next steps for the network after a bug halted the batch amendment just before activation. According to Vet, developers are preparing a new XRP software update next week that will formally deprecate the current batch amendment while work continues on a corrected version.

The issue surfaced just as the amendment needed one more validator vote to reach majority. However, developers detected a flaw in time and stopped the process before activation. Shortly after, the XRP Ledger Foundation confirmed it had received a report through its Bug Bounty program. According to the Foundation, the XRP Ledger itself remains unaffected and safe despite the amendment issue.

Also Read: Scaramucci Admits Crypto Bear Market—But Predicts Big Shift Ahead

In response, the Foundation urged validators to veto the batch amendment while engineers reviewed the report. Additionally, it stated that a fix is already underway and undergoing further validation before inclusion in a future software release. The organization also confirmed it is preparing a release that will formally deprecate the existing batch amendment.

According to Vet, the expected software update next week will handle that deprecation. He added that logical follow ups may include a detailed blog post explaining the bug. Moreover, another XRP software update could introduce a corrected batch amendment after additional testing.

Deprecation Update Set as Developers Refine Corrected Amendment

The batch transactions feature aims to allow atomic execution of multiple transactions in a single operation. Consequently, developers view it as a tool that could simplify revenue generating applications built directly on chain. The feature would also help automate transaction flows and enable paid services within apps.

Alongside the batch amendment issue, developers also identified a bug in the fixbatchinnersigs amendment. That amendment addresses how inner transactions within a batch validate signatures. Engineers continue reviewing both matters before reintroducing an updated proposal.

Separately, Ripple rotated the GPG key used to sign rippled packages. According to a notice on the XRPL blog, users must download and trust the new key to prevent upgrade issues. Automatic upgrades may not function correctly until users verify the new fingerprint.

Overall, the validator guidance and upcoming software release reflect a coordinated response. Developers paused activation before impact, validators received clear instructions, and the network continues operating without disruption as technical reviews proceed.

Also Read: Aztec (AZTEC) Price Prediction 2026–2030: Can AZTEC Hit $0.1450 Soon?

The post XRP Validator Vet Reveals What Comes Next as Batch Amendment Bug Delays Activation appeared first on 36Crypto.