XRP Ledger has moved PermissionDelegationV1_1 into its 14 day activation period after 29 of the network’s 35 trusted validators backed the account permission upgrade.
According to the live XRP Ledger amendment dashboard, the countdown began on Sept. 21 and could put PermissionDelegationV1_1 into effect on Oct. 5 at 11:18 UTC if validator support remains above the required threshold throughout the period.
At least 28 of the 35 trusted validators must continue supporting the amendment. If backing falls below that level before the countdown ends, the activation timer will reset.
PermissionDelegationV1_1 changes how an XRP Ledger account can give another account authority to perform specific tasks.
Under the current account structure, businesses that need different systems or employees to carry out operations can face the problem of giving an operational account more authority than it actually needs. Permission Delegation is designed to separate those responsibilities.
An account could, for example, authorize another account to make payments without giving it permission to change the primary account’s keys. A stablecoin issuer could keep its main keys offline while giving an internet connected compliance system permission to approve customers to hold its token.
Each delegated account can receive up to 10 permissions, while the account granting the authority retains the ability to change or revoke them.
The arrangement resembles the separation of responsibilities commonly used by financial institutions, where payment, compliance and administrative functions do not necessarily share the same level of access.
PermissionDelegationV1_1 forms part of a larger group of amendments introduced through xrpld 3.3.0. The release included BatchV1_1, ConfidentialTransfer, DynamicMPT and Sponsor alongside Permission Delegation, with several of the features geared toward institutional transactions and token issuance.
Sponsor would allow another entity to cover transaction fees and reserve requirements for users without controlling their accounts. DynamicMPT gives issuers more flexibility over selected Multi Purpose Token properties, while ConfidentialTransfer is designed to conceal MPT balances and payment amounts from public view while retaining access mechanisms for authorized parties.
Crypto.news previously reported that ConfidentialTransfer targets institutional use cases where companies may need transaction privacy while still providing information to auditors and other authorized parties.
PermissionDelegationV1_1 is the second attempt to bring delegated account permissions to the XRP Ledger.
The original amendment was stopped before reaching the main network after a community tester reported a vulnerability on Sept. 15, 2025.
Under the affected implementation, the software checked whether an account had permission to perform a transaction before properly verifying its signature. Certain rejected transactions could still incur a fee.
An attacker could therefore have submitted unauthorized transactions carrying deliberately high fees and caused another account to pay them even though the transactions were not properly signed. Repeating the process could have depleted the victim’s available XRP balance.
Validators were advised not to support the amendment after the vulnerability was discovered, preventing the affected version from activating on mainnet.
The replacement was included in xrpld 3.3.0 with changes to how unauthorized transactions are handled. Signature verification now takes place before the type of failure that could charge the targeted account.
Permission Delegation is not the only feature from the release to return after security work. BatchV1_1 replaced an earlier Batch implementation after developers found a separate critical signing vulnerability. The revised Batch upgrade has moved through validator voting after fixes and further review.
PermissionDelegationV1_1 does not directly change XRP’s supply, issuance schedule or token economics, leaving no mechanical reason for its activation alone to create substantial new demand for XRP.
The amendment deals with account permissions instead of the XRP token itself. Institutions using delegated accounts would still use XRP for the ledger’s normal fees and reserve requirements, but the feature does not require them to buy or hold large amounts of XRP simply to use delegated permissions.
Recent developments on the network show why the distinction between XRPL adoption and XRP demand matters.
A previous analysis of Ripple Prime’s XRP exposure found that even substantial institutional activity inside Ripple’s ecosystem does not automatically translate into equivalent XRP demand. Stablecoins and other issued assets can handle much of the underlying value transfer while XRP retains roles including transaction fees, reserves and some routing functions.
A similar structure applies to Permission Delegation. Stablecoin issuers, tokenized asset providers and other businesses could use the feature without making XRP the asset being transferred.
The possible price connection instead depends on whether the upgrade helps bring more activity to the XRP Ledger over time.
Institutional issuers that want to keep high authority keys offline could use delegated accounts for recurring payments or compliance tasks. If those capabilities contribute to more businesses issuing assets and processing transactions on XRPL, the resulting activity would create more use of the network, where XRP remains the native asset used for fees and reserves.
Evidence so far suggests that network growth and XRP price do not always move together. RLUSD and tokenized assets have expanded on XRPL while XRP has experienced periods of price weakness, showing that rising ledger activity does not necessarily produce immediate buying pressure for the token.
A June institutional test involving JPMorgan, Mastercard, Ondo Finance and Ripple provided another example. The tokenized Treasury redemption used the XRP Ledger, but XRP was not the asset being redeemed. Its direct role remained tied to the underlying network infrastructure.
PermissionDelegationV1_1 could therefore provide another piece of infrastructure for institutional users without becoming a major standalone XRP price catalyst.
A market reaction around activation remains possible because traders can respond to network upgrades and expectations surrounding adoption. Any sustained price effect, however, would depend on subsequent use of the feature and other market factors instead of the amendment simply switching on.
Permission Delegation is moving toward activation while several other XRP Ledger features remain at different stages of the amendment process.
BatchV1_1 is designed to bundle multiple operations into a coordinated transaction, allowing every included action to succeed or fail together. Such a structure can support settlement processes where an asset and its payment need to change hands at the same time.
ConfidentialTransfer would give Multi Purpose Token issuers the option to conceal balances and transfer amounts while leaving accounts visible. Authorized parties could still receive information needed for compliance under the proposed design.
XRPL developers have continued work beyond the 3.3.0 release. Version 3.4.0, released on Sept. 16, introduced revisions to proposed lending functions alongside another package of protocol fixes.
The lending framework remains subject to the network’s amendment process, with validator approval required before the proposed functions can become active on mainnet.
XRP