The XRP Ledger is moving closer to bank-style account controls with an upgrade that would let institutions separate payment, compliance and operational duties without handing over full contro
The XRP Ledger is moving closer to bank-style account controls with an upgrade that would let institutions separate payment, compliance and operational duties without handing over full control of their accounts.
The feature, called PermissionDelegationV1_1, allows one XRPL account to grant another account narrowly defined permissions, such as making payments or approving customers. According to official XRPL documentation, the system is designed to support role-based access control alongside existing security methods such as multi-signing.
The upgrade was originally expected to activate Oct. 5, but validator support briefly fell below XRPL’s required threshold and reset the countdown. If support remains above 80%, activation could now happen around Oct. 8.
Banks Can Separate Payments From Compliance
The practical use case is straightforward.
A stablecoin issuer could keep its most sensitive signing keys offline while allowing a separate compliance account to approve customers. Another operational account could receive permission to execute payments without gaining authority to change keys or grant additional permissions.
That resembles how traditional financial institutions already separate responsibilities across internal teams and systems.
Each delegated account can receive up to 10 specific permissions, and the primary account can later modify or revoke them.
Coinpaper previously covered the amendment when it first entered its activation window, noting that the feature could make XRPL more practical for institutional account controls.
The Upgrade Is a Second Attempt
PermissionDelegationV1_1 replaces an earlier version that was withdrawn after researchers found a critical security flaw.
The original implementation could potentially allow malicious transactions to charge unauthorized fees before signature validation was completed. The revised version changes how invalid transactions are rejected so fees cannot be deducted before the signature is properly checked.
That history makes validator approval especially important.
XRPL amendments must maintain more than 80% validator support for two consecutive weeks before activation. If support drops below the threshold, the countdown restarts. Coinpaper has previously explained how XRPL amendment voting works.
XRPL Keeps Building Institutional Controls
Permission delegation fits into a broader push to make XRPL usable by regulated financial institutions.
The network already supports permissioned domains and a permissioned DEX, allowing access to onchain markets to be restricted to wallets holding approved credentials. Developers are also exploring KYC-only liquidity pools for banks.