XRP Ledger’s Permission Delegation and Batch Upgrades Hit Mainnet This Week: What Changes

The XRP Ledger is in the middle of one of its busiest upgrade windows in months. Three protocol amendments are scheduled to switch on across October 8 and 9, 2026: one that lets accounts delegate narrow transaction powers without handing over their keys, one that bundles multiple transactions into a single all-or-nothing operation, and a security fix that has to land alongside it.

None of these changes are flashy for retail users, but together they target the kind of operational plumbing banks, payment firms and custodians ask for before they build on a public chain. Here is what each amendment does and why the timing has shifted more than once.

The Three Amendments and Their Timing

According to scheduling data reported by Coinpaper and other outlets tracking XRPL validator votes, the activation order looks like this:

• PermissionDelegationV1_1 – expected around 21:25 UTC on October 8, 2026.
• fixBatchV1_2 – expected around 14:12 UTC on October 9, 2026.
• BatchV1_1 – expected around 14:46 UTC on October 9, 2026.

On the XRP Ledger, an amendment activates only after it holds more than 80% support among trusted validators for two consecutive weeks. If support dips below that line during the countdown, the clock resets. That rule has already shaped this rollout: projected dates for both Permission Delegation and Batch moved after validator support fell below the threshold earlier in the process, which is why the activation times are best treated as scheduled rather than guaranteed until they actually fire.

Permission Delegation: Roles Without Shared Keys

Permission Delegation lets an XRPL account grant another account narrowly defined authority to submit particular transactions on its behalf, without sharing its signing keys. For an institution, that means a payments team, a compliance function and an operations desk can each hold different, limited powers over the same account rather than everyone needing access to a master key.

The “V1_1” in the name is there for a reason. As Crypto Daily reported, the original Permission Delegation amendment was found during devnet testing in September 2025 to contain a flaw that could have let unauthorized transactions charge fees to a different account. Validators declined to activate it, and the corrected V1_1 replaced it. Catching that before mainnet is a reasonable example of the amendment process doing its job.

Batch: Up to Eight Transactions, All or Nothing

BatchV1_1 allows up to eight transactions to be wrapped into a single atomic batch. Either every transaction in the bundle executes, or none of them do. That matters for settlement flows, atomic swaps and multi-step institutional transactions, where a half-completed sequence can leave a firm with an unwanted position or a reconciliation headache.

The companion amendment, fixBatchV1_2, was shipped as part of an emergency xrpld 3.4.1 release and addresses security-sensitive issues, including hardening integer arithmetic in the payment engine and correcting how Batch transactions are wrapped. Node operators running outdated software risk becoming “amendment blocked,” meaning their servers can no longer follow the ledger once the change activates.

Why This Fits a Wider Pattern

The XRPL upgrades are part of a broader trend of public blockchains competing on unglamorous settlement features rather than headline throughput. We made a similar argument about Solana’s delivery-versus-payment tooling: atomic settlement, role separation and predictable failure modes are what institutions evaluate before committing real volume.

Ethereum is moving through its own staged process, as we covered in our piece on the Glamsterdam upgrade heading to Sepolia, and like the XRPL amendments, those dates have been conditional on testing and coordination going smoothly.

What It Means for Users

For most XRP holders, nothing changes day to day. Wallets and exchanges will need to add support before ordinary users see delegation or batching in an interface. The more immediate audience is developers and node operators, who should make sure they are running current xrpld software ahead of the activation windows.

It is also worth separating protocol progress from market sentiment. Reporting this week showed demand for XRP exchange-traded funds cooling sharply week over week, and the wider market has been under pressure from rising Treasury yields. Feature upgrades like these play out over months and years of adoption, not in a single day’s price action.

This article is for informational purposes only and does not constitute financial advice.