The XRP Ledger activated PermissionDelegationV1_1 on Oct. 8, allowing account owners to delegate specific operational powers to separate accounts without sharing the master keys that control their main holdings. The upgrade, confirmed by monitoring site XRPL Dashboard, gives banks, stablecoin issuers and tokenized-fund operators a way to enforce internal separations of duty directly on the ledger.

The feature addresses a long-standing operational tension in institutional crypto: businesses running routine transactions need signing keys available throughout the day, yet keeping broadly empowered keys on internet-connected machines multiplies the damage a hacker could cause if that machine is compromised. Delegation splits that authority by job. A stablecoin issuer can authorize a compliance account to approve new customers while its main keys stay offline. The helper signs with its own keys, can perform only granted actions, and the owner can change or withdraw permissions at any time.

What does the upgrade change in practice?

Each delegated account can hold up to 10 permissions. These restrict the types of actions a helper can perform rather than imposing automatic spending caps — a design choice that shifts responsibility for transaction limits onto the delegating business's own controls. Banks already separate payment and compliance duties among staff; the upgrade makes those divisions enforceable at the protocol level rather than relying purely on internal policy.

Activation required more than 80% support from trusted validators, the operators who confirm transactions, sustained for two consecutive weeks. With the current validator list of 35, that means at least 29 supporters. The countdown had reset in September after support slipped below the threshold, forcing a retry, as CoinDesk previously reported.

The upgrade arrives as the network carries meaningful institutional volume. The ledger held an average of $3.72 billion in tokenized assets and $539 million in Ripple's RLUSD stablecoin during the second quarter, according to a report shared with CoinDesk by Evernorth, an XRP treasury company. Together, those balances amounted to about $4.26 billion.

What flaws remain open?

Official guidance currently tells users not to delegate the PaymentBurn permission until a separate fix activates. Under certain conditions, that permission — intended to let a helper destroy tokens — also allows the helper to create new issued tokens. The warning applies to tokens issued on the ledger, not to newly minted XRP, and other granular permissions are unaffected.

Developers are also examining a bug in how some XRP Ledger servers tally amendment votes. A report filed Oct. 8 found that some servers drop a validator from their count after it rotates a routine security key, even while that validator remains online and voting. A server that loses track of two validators would measure support against 33 instead of 35, making a proposal appear closer to passing on that server's local count than it actually is. A proposed patch would have servers identify validators by a permanent ID instead of their keys; it remains under review.

When will the PaymentBurn warning lift?

The fix for the PaymentBurn issue held 27 of 35 validator votes as of Friday. It needs 29 to start the two-week countdown that would activate the amendment and lift the official warning. Until then, institutions adopting the new delegation model should restrict delegated permissions to the unaffected granular actions while the amendment window runs its course.