The XRP Ledger is moving closer to activating a major new feature called PermissionDelegationV1_1 after receiving support from 29 of its 35 trusted validators.
The amendment has now entered a 14-day activation period. If validator support stays above the required 80% threshold, the feature is expected to go live on October 5.
For activation to happen, at least 28 of the 35 validators must continue supporting the proposal throughout the entire countdown period. If support drops below that level, the timer will reset.
Permission Delegation is designed to give XRP Ledger accounts more flexibility and security. Instead of handing over full account control, users and businesses will be able to grant specific permissions to another account.
For example, a company could allow an account to process payments without giving it access to change security settings or account keys. A stablecoin issuer could keep its main keys safely offline while allowing a separate system to handle customer approvals and compliance tasks.
Each delegated account can receive up to 10 specific permissions, while the main account keeps full control and can change or remove those permissions at any time.
The feature is aimed at making the XRP Ledger more attractive for businesses and institutions that need different employees or systems to perform separate tasks without sharing complete account access.
PermissionDelegationV1_1 is part of a broader set of upgrades introduced in xrpld 3.3.0. Other features include BatchV1_1, ConfidentialTransfer, DynamicMPT, and Sponsor. Many of these upgrades are focused on helping institutions use the network more efficiently.
Sponsor would allow one party to cover transaction fees for another user without controlling their account. DynamicMPT gives token issuers more flexibility, while ConfidentialTransfer is designed to provide transaction privacy while still allowing access for authorized auditors and regulators.
This is actually the second attempt to introduce Permission Delegation to the XRP Ledger.
An earlier version was stopped in September 2025 after community testers discovered a security flaw. The issue could have allowed attackers to create unauthorized transactions with high fees, potentially causing victims to lose XRP.
After the problem was found, validators were advised not to support the amendment, preventing it from reaching the main network.
Developers later fixed the vulnerability by changing the way transaction signatures are verified. The updated version was included in xrpld 3.3.0 and is now moving through the activation process.
Many XRP holders are wondering whether this upgrade could affect XRP’s price.
The feature itself does not change XRP’s supply, token economics, or issuance schedule. Because of that, there is no direct reason for the amendment alone to create major demand for XRP.
Permission Delegation focuses on account management and security rather than the XRP token itself. Companies using the feature will still pay normal network fees in XRP, but they will not necessarily need to buy large amounts of the asset just to use delegated permissions.
The real impact could come from increased adoption of the XRP Ledger. If the new feature makes the network more attractive for businesses, stablecoin issuers, and tokenized asset providers, overall activity on the ledger could grow.
More activity would mean more transactions, which increases the use of XRP for fees and reserve requirements. However, history has shown that higher network activity does not always lead to immediate price increases for XRP.
Recent growth in projects such as RLUSD and tokenized assets has brought more activity to the XRP Ledger, but XRP’s price has not always moved higher alongside that growth.
The same situation could apply to Permission Delegation. The feature may help strengthen the network’s infrastructure and attract more institutional users, but any long-term effect on XRP’s price would depend on how widely it is adopted and overall market conditions.
The XRP Ledger continues to add new tools aimed at institutional users. Alongside Permission Delegation, developers are working on upgrades for transaction batching, privacy features, token management, and lending services.
While these improvements could make the network more useful for businesses and financial institutions, their success will ultimately depend on real-world adoption after they go live.
