Home » Blockchain » XRP Ledger Permission Delegation V1.1: What It Does and Its Limits

XRP Ledger Permission Delegation V1.1: What It Does and Its Limits

Permission Delegation V1.1 lets an XRP Ledger account give another account limited powers without sharing its keys. It was reported live on October 8, with one permission still carrying a…

Abstract padlock and keyboard imagery symbolizing XRP Ledger permission delegation and secure digital access control

The quick take

  • Permission Delegation V1.1 is an XRP Ledger amendment that lets one account give another account limited powers without handing over its main signing key.
  • It shipped in xrpld 3.3.0 on August 6, 2026 and replaces an original amendment that contained a critical bug.
  • Analytics Insight reported it went live late on Thursday, October 8, 2026, after a two-week validator approval period.
  • One permission, PaymentBurn, carries an official warning for now.

How delegation works

An account owner, called the delegator, authorizes a second account, the delegate, to perform specific actions. Each delegate can receive up to 10 permissions. Those permissions limit which actions the delegate can take, but they do not set spending limits. The owner can change or revoke permissions later, and EdgeX’s summary of the announcement says revocations take effect immediately. Some account-level controls stay with the main account.

So the master key isn’t gone. The main account keeps its keys and can revoke access. Delegation just reduces how often the master key has to be used for routine actions.

Examples cited by the outlets include a stablecoin issuer giving a compliance account approval authority only, and the owner of a blackholed issuer account delegating tasks such as domain management before locking its keys. Ripple’s Lauren Berta linked the feature to regulated assets such as RLUSD, which the RLUSD team is reported to be testing in a development environment.

Why there is a V1.1, and how it got approved

The xrpld 3.3.0 release notes say V1.1 replaces the original amendment and fixes a critical bug in it. The notes also list changes that reject delegation to pseudo-accounts and block delegated transactions from being queued. Reporting on the retry does not agree on the exact bug, and we could not open an official description, so we do not describe it further.

The network needs at least 29 of 35 validators to hold support for 14 days. Amendments take effect on flag ledgers, which occur about every 16.5 minutes.

Date Event Source
Aug 21 7 of 35 trusted validators in support; Ripple voted yes Coingape
Sept 21 to 24 29 validators in support, starting a 14-day window (outlets give slightly different start dates) EdgeX, Analytics Insight
Oct 8 Reported live late in the day, with 30 votes in the latest period Analytics Insight (Oct 9)

Who Benefits and How

The people who gain most are account holders who run shared or institutional XRP Ledger accounts, such as stablecoin issuers. They can hand a compliance or admin task to another account without sharing the main key, and take the access back if needed. Ordinary XRP holders see no direct change. Whether any bank or credit union uses the feature is unconfirmed, and the amendment was reported live on October 8, 2026, so confirm on a live amendment tracker before relying on it.

Limits and open questions

  • Analytics Insight reports official XRPL guidance warning against delegating the PaymentBurn permission until a separate fix takes effect. The permission normally lets an account destroy issued tokens, but under certain conditions it can also create them. The issue affects issued assets, not new XRP, and other permissions are unaffected.
  • That follow-up fix had 27 of the 29 votes it needed to start its own countdown as of the October 9 report.
  • Permissions limit actions, not amounts. A delegate with a payment permission is not capped by a dollar limit.
  • Activation is reported by a single outlet citing a dashboard. We could not open the XRPL.org page to confirm.
  • This post is not security or investment advice.

Frequently Asked Questions

Which permission should issuers avoid delegating?

Official XRPL guidance, as reported, says to avoid delegating PaymentBurn until the separate fix is active.

Can a delegate move all of an account’s funds?

Only if the owner grants a permission that allows it. Owners should grant the narrowest set of permissions that works.

Is it live?

It was reported live on October 8, 2026, by Analytics Insight. Confirm on a live amendment tracker.

Sources

Related Reading