What is the XRP Ledger Permission Delegation feature that activated on October 8, 2026, and what can a delegate account do?

The full answer

What does Permission Delegation let an account do?

Permission Delegation lets one XRP Ledger account hand another account a set of narrow rights. XRPL.org’s release notes for xrpld 3.3.0, published August 6, 2026, describe the PermissionDelegationV1_1 amendment as granular account permission delegation that “allows accounts to delegate some permissions to other accounts” [1].

Analytics Insight reported on September 25, 2026 that account owners could delegate specific actions without granting full control, that each delegate can receive up to 10 permissions, and that the main account can revoke them [2]. Its example was a payments desk given authority to process transactions. The same report said stablecoin issuers and custodians could run daily operations from internet-connected systems while keeping higher-level account keys offline [2].

Ripple’s president, Monica Long, pointed to permission delegation and confidential transfers as tools for institutional tokenization, TokenPost reported on September 30, 2026 [5]. For other controls aimed at regulated firms, see what compliance features the XRP Ledger offers institutions.

What can a delegate account not do?

In the Analytics Insight example of September 25, 2026, the payments desk gains authority to process transactions without gaining permission to change critical security settings [2]. The owner keeps the power to revoke the delegate’s permissions [2].

XRPL.org’s 3.3.0 notes add two hard limits in the server code. Delegating permissions to pseudo-accounts is rejected, and delegated transactions are blocked from being queued [1]. The August and September 2026 coverage did not spell out which transactions can never be delegated.

Did Permission Delegation activate on October 8, 2026?

The vote was close through late September. Analytics Insight reported on September 25, 2026 that PermissionDelegationV1_1 entered its 14-day activation countdown on September 21 with 29 of 35 trusted validators in support, and could activate on October 5 if support stayed at or above 80% [2].

Analytics Insight reported on September 25, 2026 that PermissionDelegationV1_1 entered its 14-day activation countdown on September 21 after 29 of 35 trusted validators supported it, and that it could activate on October 5 if support stayed at or above the 80% threshold. Analytics Insight reported on September 25, 2026 that the amendment entered its 14-day countdown on September 21 with 29 of 35 trusted validators in support [2]. A lost majority stops the countdown, so the October 5 date held only while support stayed at or above the threshold.

XRPL.org’s release notes of August 6, 2026 came before the vote and give no activation date [1]. The October 8, 2026 date in the question therefore rests on later reporting, and none of the dated vote counts above records the final run of support. How amendment votes work is covered in how XRP Ledger upgrades get approved.

Why was a second version of the amendment needed?

The first attempt failed on a test network. Ripple wrote on September 22, 2025 that XRPL version 2.5.0, published that June, introduced Permission Delegation among other amendments [4]. XRPL.org then disclosed on September 29, 2025 that a bug in it allowed an account to charge transaction fees to any other account, and could have been used to drain an account’s XRP balance; the feature was not enabled on mainnet [3].

Analytics Insight added detail on September 25, 2026. A community tester found the flaw, which let an attacker make another account pay fees for improperly signed transactions, and validators rejected that amendment before activation [2]. The replacement, it said, changes how the network handles unauthorized transactions so that fees are not charged before signature verification [2]. XRPL.org’s own notes say PermissionDelegationV1_1 replaces the original amendment, “fixing a critical bug discovered in the original implementation” [1].

What else did xrpld 3.3.0 change around delegation?

Several smaller changes in the same release touch delegated activity. XRPL.org listed a new delegate filter parameter for the account_tx method, which lets servers return transactions by delegate [1]. The bug fixes include the pseudo-account and queuing blocks noted above, plus a change that uses the direction of a trust line balance to validate IOU PaymentMint and PaymentBurn [1]. The full release is summarised in what is new in xrpld 3.3.0, and the wider list of features sits in what the XRP Ledger has today and what is coming.

What is the strongest case for caution?

The feature’s history is the main critique. XRPL.org said in September 2025 that the first version could have drained an account’s XRP through fees [3], and called it a critical bug when it shipped the replacement in August 2026 [1]. Analytics Insight reported on September 25, 2026 that 29 of 35 trusted validators supported the amendment when its countdown began on September 21 [2]. Any account that grants a delegate rights is relying on code that validators were still debating weeks before the reported activation.