TLDR
- PermissionDelegationV1_1 entered a 14-day activation countdown after 29 of 35 validators backed the amendment.
- The upgrade could activate on October 5 if validator support stays at or above the required 80% threshold.
- XRP Ledger accounts could delegate specific payment and compliance duties without sharing full account control.
- The new version replaces an earlier proposal that contained a flaw linked to unauthorized transaction fee charges.
- The fix in xrpld 3.3.0 changes authorization checks so failed transactions cannot charge fees before signature verification.
An XRP Ledger account may soon let another account make payments or approve customers without giving away full control. PermissionDelegationV1_1 entered a 14-day activation period on September 21 after 29 of 35 validators backed the amendment. The change could activate on October 5 at 11:18 UTC if support stays above the required 80% level.
XRP Ledger Moves Toward Split Account Duties
The amendment lets an account assign narrow permissions to another account. A stablecoin issuer could let a compliance system approve customers while keeping its keys offline. Another operations account could receive payment rights without gaining power to change keys or appoint new delegates.
Each delegate can hold up to 10 permissions, and the main account can change or revoke them. The structure mirrors how financial firms separate payment, compliance, and security duties. Recent XRPL development also added AI payment tools for automated services, widening the network’s payment tools.
Validator Support Starts Activation Countdown
At least 28 of the 35 validators must continue supporting PermissionDelegationV1_1 during the countdown. If support falls below that threshold, the activation timer resets. The rule gives validators time to review the amendment before the network enables it.
The vote arrives as other XRP Ledger upgrades move through the amendment process. The Batch V1.1 upgrade showed strong validator support this week, with network changes focused on transaction handling and account functions. PermissionDelegationV1_1 could add another option for businesses that need separate, specific operational roles.
Security Fix Replaces Earlier Version
PermissionDelegationV1_1 replaces an earlier proposal that contained a fee-related security flaw. A community tester found the issue in September 2025 before mainnet activation. The flaw could have let an attacker submit transactions that forced another account to pay fees before the system confirmed a valid signature.
Developers changed the rejection process in xrpld 3.3.0 so the server checks authorization without charging the target account first. The update follows new wallet growth, with 3,647 wallets added during XRP’s latest move as developers prepared several amendments.
The new version keeps the delegation model but changes how failed transactions receive checks. If validator support remains above 80%, the XRP Ledger can activate the amendment on October 5. Account owners would then gain a way to divide routine duties while keeping full account control under separate keys.
