Swan.my.id — Jakarta - The XRP Ledger upgrade is moving toward a potential activation in October 2026, with PermissionDelegationV1_1 at the center of the proposed changes. The amendment could introduce a more flexible way to manage account permissions on the blockchain.
The upgrade entered its 14-day activation period on September 21 after receiving support from 29 of 35 trusted XRP Ledger validators. If support remains at or above the required 80% threshold, the amendment could become active on October 5.
The proposed change is particularly relevant to institutional users. It allows an account owner to delegate specific permissions to another party or system without giving that party complete control over the account.
XRP Ledger Upgrade Targets Flexible Account Access
The main change in the XRP Ledger upgrade is the introduction of more detailed permission management. Instead of giving another user full access, an account owner can assign specific tasks.
This approach resembles access-control systems commonly used by financial institutions. Banks, for example, often separate responsibilities among payment teams, compliance departments, and security personnel.
Under PermissionDelegationV1_1, an account can grant selected permissions to other parties. Each delegate can receive up to 10 specific permissions. The account owner can also revoke those permissions when they are no longer needed.
As a result, different operational functions could work with the same account without receiving identical levels of authority.
For example, a compliance system could receive permission to handle a defined approval process. However, that system would not necessarily receive permission to move funds or perform unrelated account operations.
This structure could make the XRP Ledger more adaptable to organizations that require strict separation of duties.
Why the Upgrade Matters for Banks
Financial institutions generally operate with multiple layers of authorization. A payment employee may need to process transactions, while a compliance team reviews customer activity. Meanwhile, security teams may monitor access and system behavior.
The proposed XRP Ledger upgrade introduces a similar concept at the blockchain account level.
The system could potentially support use cases involving banks, stablecoin issuers, and custodians. These organizations may need multiple operational systems to interact with an account while keeping final control with the account owner.
However, the upgrade does not mean that specific banks have already adopted XRP Ledger.
There is also no indication in the supplied material that a particular bank has begun using PermissionDelegationV1_1. Instead, the amendment provides infrastructure that could better match institutional access requirements if organizations choose to use it.
Besides institutional applications, the concept may also be relevant to businesses operating automated blockchain systems. Delegated permissions could allow software to perform limited functions without receiving unrestricted account authority.
That distinction is important. The feature changes what the XRP Ledger can support, but adoption will still depend on individual organizations and their technical requirements.
XRP Ledger Upgrade Follows Earlier Security Issue
PermissionDelegationV1_1 is not the first attempt to introduce this type of functionality to the XRP Ledger.
An earlier version was introduced through xrpld 2.5.0 in 2025. However, the proposal was withdrawn in September 2025 after community testers discovered a security issue on the test network.
The vulnerability involved transaction fees and unauthorized signatures. Under certain circumstances, an attacker could potentially make another account pay fees for transactions that had not been properly authorized.
Repeated exploitation could have resulted in XRP being consumed through transaction fees.
The amendment was rejected by validators before it could become active on the production network. Developers then prepared a replacement approach through xrpld 3.3.0.
The newer implementation changes how transactions without valid authorization are processed. The goal is to prevent transaction fees from being charged before the required signature verification succeeds.
This history explains why the latest proposal has gone through additional testing and validation before activation.
What Could Change After October 5?
If the amendment maintains the required validator support throughout the activation period, PermissionDelegationV1_1 could become active on October 5, 2026.
Several changes could then become relevant for XRP Ledger users:
- Specific permissions: Account owners could delegate selected functions instead of giving full account access.
- Multiple delegates: Different parties or systems could receive different permissions.
- Revocable access: Permissions could be withdrawn by the account owner.
- Institutional flexibility: Banks and other financial organizations could potentially separate operational roles.
- Limited authority: Delegated users would not automatically receive complete control over the underlying account.
These changes could make account administration more flexible. They may also reduce the need to share broad account authority when only a limited function is required.
However, the actual impact will depend on how developers and organizations implement the feature.
October 5 Is Still a Potential Activation Date
Although October 5 has emerged as the potential activation date, it should not be treated as a guaranteed launch date.
The amendment entered its activation period after 29 of 35 trusted validators supported it. That represents support above the stated 80% requirement.
However, validator support must remain at the required level during the activation period. If support falls below the threshold, the amendment may not activate as scheduled.
Therefore, the October 5 date remains conditional.
This distinction is important for users following developments around XRP Ledger. A proposed protocol change can reach the activation stage without necessarily becoming active on the initially expected date.
The final outcome depends on the network's governance process and validator support.
What Permission Delegation Means for XRPL Users
For ordinary XRP Ledger users, the change may not immediately alter everyday transactions.
The most significant implications are likely to appear in applications that require multiple users, automated systems, or institutional controls.
A business could potentially assign specific responsibilities to separate systems. Meanwhile, the main account could retain control over broader functions.
This could also help developers design applications with more granular access policies. Instead of treating account access as an all-or-nothing decision, applications could work with defined permissions.
Nevertheless, users should distinguish between technical capability and actual adoption. A protocol upgrade can provide new functionality, but companies still need to integrate and use it.
The same applies to financial institutions. The availability of institutional-style permission controls does not prove that banks or stablecoin issuers are already using them.
What to Watch Before the Upgrade
Several developments could determine whether the proposed upgrade activates as scheduled.
First, users should monitor validator support during the activation period. The 80% threshold remains central to the process.
Second, developers and businesses may provide more information about potential applications after the amendment becomes active.
Third, security performance will remain important because the proposal follows an earlier version that was withdrawn after a testnet vulnerability was identified.
For XRP Ledger users, the upgrade therefore represents more than a new feature. It also reflects the network's effort to introduce institutional-style access controls while addressing security concerns identified during earlier testing.
Conclusion
The XRP Ledger upgrade centered on PermissionDelegationV1_1 could introduce a more flexible approach to account permissions. The feature allows account owners to delegate specific functions without transferring complete control.
That model could be useful for institutions that separate payment, compliance, security, and other operational responsibilities.
However, October 5, 2026 remains a potential activation date rather than a guaranteed one. Validator support must continue meeting the required threshold throughout the activation period.
The proposal also comes after an earlier version was withdrawn following a security issue on the test network. Its replacement reflects changes designed to address the transaction authorization and fee-related problem.
If activated, PermissionDelegationV1_1 could give developers and institutional users another tool for managing access on the XRP Ledger. Its longer-term significance will depend on actual adoption and implementation across the ecosystem.
FAQ: XRP Ledger Upgrade
What is PermissionDelegationV1_1?
PermissionDelegationV1_1 is a proposed XRP Ledger amendment that allows account owners to delegate specific permissions without giving another party full account control.
Why is the XRP Ledger upgrade relevant to banks?
The feature can support separate permissions for different operational functions. This resembles access controls commonly used in financial institutions.
Are banks already using PermissionDelegationV1_1?
The supplied material does not identify a specific bank using the feature. The amendment is still moving through the activation process.
When could the XRP Ledger upgrade become active?
The potential activation date is October 5, 2026, provided validator support remains above the required 80% threshold.
How many permissions can a delegate receive?
According to the supplied material, each delegate can receive up to 10 specific permissions.
Can delegated permissions be revoked?
Yes. The account owner can revoke delegated permissions when necessary.
Does the upgrade guarantee greater security?
The feature is designed to provide more granular access control. However, its security impact will depend on implementation and how users configure delegated permissions.