Six major XRP Ledger amendments introduced with the network’s xrpld 3.3.0 software release have reached the end of their initial two-week validator voting window, putting a package of privacy, payments and tokenization upgrades closer to potential Mainnet activation.
The amendments were introduced when XRP Ledger developers released xrpld 3.3.0 on August 6. They include BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, Sponsor and fixCleanup3_3_0.
Under XRP Ledger’s amendment process, however, two weeks passing after a proposal becomes available for voting does not automatically activate it.
An amendment must receive support from more than 80% of trusted validators and then maintain that supermajority continuously for two weeks. If support falls to 80% or below during that period, its majority is lost and the two-week timer must begin again if support subsequently recovers.
That distinction means each amendment’s activation depends on when it individually crossed the 80% threshold and whether it maintained sufficient validator support afterward, rather than simply the August 6 software release date.
Six Amendments Target Institutional XRP Ledger Use
ConfidentialTransfer is among the most significant proposals. Based on XLS-96, it introduces privacy-preserving transfers for Multi-Purpose Tokens, or MPTs, allowing transaction amounts and balances to be concealed while retaining the ledger infrastructure needed for tokenized assets.
The feature is particularly relevant to XRP Ledger’s institutional tokenization ambitions. More than $530 million of tokenized real-world assets excluding Ripple’s RLUSD stablecoin were already tracked on XRPL when the upgrade was released, according to CoinDesk.
BatchV1_1, based on XLS-56, enables atomic batch transactions. Multiple transactions can be grouped so that they execute together according to the batch rules, improving workflows that currently require several independent ledger operations.
Sponsor, based on XLS-68, introduces mechanisms for another account to cover reserves and transaction costs. The feature could reduce onboarding friction by allowing applications or institutions to absorb blockchain-related costs instead of requiring every new user to independently maintain XRP for network expenses.
PermissionDelegationV1_1 adds granular account permission delegation, allowing accounts to authorize other parties to perform defined actions without surrendering unrestricted control.
DynamicMPT expands Multi-Purpose Token functionality by introducing token properties that issuers can make permanently immutable, while fixCleanup3_3_0 bundles amendment-gated corrections to existing network behavior.
Activation Depends on Sustained 80% Validator Support
XRP Ledger’s amendment system is designed to prevent software developers from unilaterally changing consensus rules.
Validators submit their amendment votes as part of validation messages. Every 256th ledger is a “flag ledger,” when servers evaluate those votes. Once an amendment exceeds 80% support, the ledger records that it has achieved majority status and begins measuring the two-week period.
If the supermajority survives continuously for two weeks, an EnableAmendment pseudo-transaction permanently activates the change. The new rules begin applying from the following ledger.
The mechanism also has operational consequences for infrastructure providers. Once an amendment activates, servers running older xrpld versions that do not understand the new consensus rules can become amendment-blocked, preventing them from processing the ledger correctly until they upgrade.
Version 3.3.0 simultaneously retired five older amendments — Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve and fixUniversalNumber — by incorporating their already-active behavior permanently into the protocol.
The latest voting cycle therefore represents more than routine maintenance. If the six proposals ultimately secure the required sustained validator support, XRPL would gain a combination of privacy, transaction batching, sponsored network costs and more flexible token controls aimed directly at institutional payments and tokenized-asset infrastructure.
