XRPXRP, coin
DevelopingSecurity

XRPL validators move BatchV1_1 amendment toward conditional Sept. 29 activation

CryptoSlate reports XRPL validators support the repaired BatchV1_1 amendment, which would activate on Sept. 29 if support holds above 80% for two weeks.

Why it matters

The activation date depends on validator support holding above 80% for the full two-week period, and operators running outdated nodes or clients could see failures once it goes live. Because only one outlet has covered the story, its account of the amendment state and the client-side risk is not independently confirmed.

Key facts

XRP Ledger validators have put the repaired BatchV1_1 amendment on a conditional path to activate at 14:06:41 UTC on Sept. 29.

Reported by CryptoSlate

The BatchV1_1 rewrite closes a critical authorization flaw and enables multi-transaction batches with four execution modes.

Reported by CryptoSlate

xrpldashboard showed 30 of 35 trusted validators supporting the amendment on Sept. 22, above the displayed 28-vote threshold.

30Reported by CryptoSlate

A validator majority for the amendment first appeared on-ledger on Sept. 15.

Reported by CryptoSlate

XRPL amendment rules require support to remain above 80% for two weeks, and a fall to 80% or less ends the majority period.

80 %Reported by CryptoSlate

Researchers found a critical authorization flaw in February while the original Batch amendment was still in its voting phase, and validators were advised to vote it down.

Reported by CryptoSlate

The original Batch amendment never activated on the XRP Ledger mainnet.

Reported by CryptoSlate

XRPL Labs' official vulnerability disclosure states that no funds were at risk from the flaw.

Reported by CryptoSlate

What happened

CryptoSlate reported that XRP Ledger validators have placed the repaired BatchV1_1 amendment on a conditional path to activating at 14:06:41 UTC on Sept. 29. The rewrite closes a critical authorization flaw found in February while the original Batch amendment was still in its voting phase, and it adds multi-transaction batches with four execution modes. According to CryptoSlate, xrpldashboard showed 30 of 35 trusted validators supporting the amendment as of Sept. 22, above the displayed 28-vote threshold, and a majority first appeared on-ledger on Sept. 15. XRPL amendment rules require support to stay above 80% for two weeks, so a drop to 80% or less would end the majority period and cancel the activation date. The original Batch amendment never activated on mainnet; validators were advised to vote it down, and XRPL Labs' official vulnerability disclosure states that no funds were at risk. CryptoSlate also notes that outdated nodes and clients may fail after activation and that outer success can still conceal failed inner transactions, leaving client software exposure open at the activation date.

How the story developed

  1. First report

    First report by CryptoSlate

    XRPL fixes critical pre-mainnet flaw, but client apps remain at risk

    CryptoSlate

  2. Update

    Authorization flaw found in Batch amendment during voting phase

    Researchers found a critical authorization flaw in February, validators were advised to vote it down, and XRPL Labs' vulnerability disclosure said no funds were at risk.

    CryptoSlate

  3. Update

    Validator majority for the repaired amendment appears on-ledger

    A majority for the amendment first appeared on-ledger on Sept. 15.

    CryptoSlate

  4. Update

    Validator support reported above the 28-vote threshold

    xrpldashboard showed 30 of 35 trusted validators supporting the amendment on Sept. 22.

    CryptoSlate

Affected entities

Original sources

PublisherReportRolePublished
CryptoSlate
Crypto media
XRPL fixes critical pre-mainnet flaw, but client apps remain at riskOriginal