XRP Ledger Batch Amendment: Why September 29, 2026 Is a Hard Deadline for Node Operators

On September 29, 2026 at 14:06:41 UTC, a protocol upgrade on the XRP Ledger arms itself: the batch amendment carrying the internal name BatchV1_1. If you hold XRP on an exchange or in a custodial wallet, there is nothing for you to do. If you run a node of your own, or run a service against a node of your own, this date is a hard deadline, after which your server drops out of the network.

This article explains what the amendment changes, where the date comes from, how to check the status yourself and which caveats are attached to the date. Every figure in this article comes from the validated ledger and from the protocol documentation, not from announcements.

What an amendment on the XRP Ledger is and why it needs no shutdown date

An amendment is a change to the rules of the XRP Ledger protocol that the network's trusted validators vote on, rather than a company scheduling it. That is what separates the process from a classic hard fork with an announced block height: there is no calendar entry that somebody sets, only a condition that the network either meets or does not.

The rule behind it is written into the protocol documentation and it is short. An amendment needs the approval of more than 80 percent of the trusted validators, and it has to hold that approval continuously for two weeks. Only then is it activated. Should approval slip below the threshold at any point during those two weeks, even briefly, the count starts again from the beginning.