[REVISION HISTORY]

XRP Ledger protocol amendments and upgrades

Updated 3 times since CLSTR started tracking revisions of this situation.

What changed

2026-10-23 23:22 UTC → 2026-10-25 10:23 UTC · added ~~removed~~

The XRP Ledger (XRPL) has successfully activated two major protocol upgrades: PermissionDelegationV1_1 and BatchV1_1. Both amendments required a supermajority of validator support to pass. PermissionDelegationV1_1, following the XLS-75 technical standard, allows account holders to assign up to ten specific transaction permissions to separate accounts. This enables organizations to manage operations like treasury management or stablecoin issuance without exposing master private keys, mimicking traditional finance controls. However, developers have cautioned against delegating the ‘PaymentBurn’ permission due to an existing vulnerability that could allow unauthorized token creation. BatchV1_1 enables the bundling of two to eight transactions into a single atomic operation. This includes an ‘all-or-nothing’ mode, ensuring that if one step in a sequence fails, the entire operation is reversed. This feature is intended to support complex workflows such as NFT swaps, over-the-counter trades, and delivery-versus-payment settlements. To prepare for these changes, developers released xrpld 3.4.1 to address minor issues via the fixBatchV1_2 amendment, noting that no user funds were impacted. While these upgrades represent a significant step toward institutional adoption, a separate issue regarding validator vote counting has been identified for future resolution. Recent governance efforts have focused on the fixCleanup3_4_0 maintenance amendment, which aims to address technical issues including precision and rounding corrections for vault transactions, lending default processing, and asset freezing. The activation of this update was rescheduled to November 4 after validator support briefly fell below the required 80% threshold on October 21, triggering a mandatory reset of the 14-day countdown. As of October 24, support has recovered to 32 out of 35 trusted validators (91.43%), though the November 4 activation remains conditional on maintaining uninterrupted consensus.

Versions

Only revisions since CLSTR began indexing content versions appear here. Select a version to see what changed compared to the one before it.