XRPXRP, coin
DevelopingProtocol update

XRP Ledger Batch V1.1 amendment set to activate on October 9 after timer reset

U.Today reports the XRP Ledger Batch V1.1 amendment will activate on mainnet on October 9, 2026, alongside the fixBatchV1_2 fix.

Why it matters

If Batch activates as described, XRP Ledger gains atomic multi-transaction execution, so a failed transaction inside a batch would undo the whole group rather than settle partially. The story is a single-outlet report on a scheduled protocol change, and no market or regulatory consequence is documented in the evidence available.

Key facts

Batch V1.1 is scheduled to be deployed on the XRP Ledger mainnet with activation set for October 9, 2026.

Reported by U.Today

Batch V1.1 is a replacement amendment that ships the fixed Batch implementation included in the xrpld v3.3.0 release.

Reported by U.Today

Batch had earlier gained majority validation and was set to activate on September 29, 2026 before its activation timer was reset.

Reported by U.Today

The timing shifted after the amendment was temporarily rejected, restarting the two-week activation window.

Reported by U.Today

U.Today reports a minor issue was detected with the fix included in the xrpld 3.4.1 release.

Reported by U.Today

XRP community validators flipped their votes to allow Batch to launch at the same time as its fix update.

Reported by U.Today

Batch, also known as XLS-56, lets multiple XRPL transactions from multiple accounts execute atomically in a single ledger close.

Reported by U.Today

In the feature's all-or-nothing mode, a failed inner transaction rolls back the entire batch.

Reported by U.Today

What happened

U.Today reports that Batch V1.1, a replacement amendment carrying the fixed Batch implementation from xrpld v3.3.0, is scheduled for deployment on the XRP Ledger mainnet in five days, with XRPScan data putting the activation date at October 9, 2026. The same outlet reports the timing moved after Batch was temporarily rejected, which restarted the two-week activation window, and that the amendment had already gained majority and was set to activate on September 29, 2026. U.Today says a minor issue was found in the fix shipped in the xrpld 3.4.1 release, after which XRP community validators flipped their votes to let Batch launch at the same time as its fix update. Batch is the XLS-56 proposal, which lets several transactions from several accounts execute atomically within one ledger close, and rolls the whole batch back when an inner transaction fails in all-or-nothing mode. Only U.Today covers this, so the activation date, the rejection episode and the nature of the xrpld 3.4.1 issue rest on that single report.

How the story developed

  1. First report

    First report by U.Today

    Five Days Left for Key XRP Transaction Upgrade: What Comes Next?

    U.Today

  2. Update

    Batch gains majority and targets September 29 activation

    Batch had reached majority validation and was set to activate on the XRP Ledger mainnet on September 29, 2026.

    U.Today

  3. Update

    Amendment temporarily rejected, activation timer restarted

    The two-week activation window was restarted after the amendment was rejected, pushing the activation date back.

    U.Today

  4. Update

    Minor issue found in the xrpld 3.4.1 fix

    A minor issue was detected in the fix shipped in the xrpld 3.4.1 release, which U.Today links to the rejection.

    U.Today

  5. Update

    Validators pair Batch with its fix update

    XRP community validators flipped their votes so Batch would launch alongside its fix, with Batch V1.1 as the replacement amendment carrying the implementation from xrpld v3.3.0.

    U.Today

  6. Update

    October 9 activation date set

    XRPScan data puts Batch activation at October 9, 2026, the same day as the fixBatchV1_2 amendment.

    U.Today

Affected entities

Original sources

PublisherReportRolePublished
U.Today
Crypto media
Five Days Left for Key XRP Transaction Upgrade: What Comes Next?Original