TL;DR
Get hardware and tech essentials delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The XRP Ledger activated PermissionDelegationV1_1 on Oct. 8, letting account owners authorize other accounts to perform specified tasks without sharing primary keys. The network warns users not to delegate PaymentBurn until a separate fix is approved and activated.
The XRP Ledger activated PermissionDelegationV1_1 on Oct. 8, enabling account owners to authorize other accounts to perform selected tasks without sharing the keys that control the owner’s account. The change could let businesses, including banks and stablecoin issuers, separate payment and compliance functions on-ledger, but users have been warned not to delegate one permission, PaymentBurn, until a separate fix takes effect.
The feature allows a helper account to sign with its own keys and carry out only the actions assigned to it. An owner can grant a helper up to 10 permissions, then change or withdraw them. The permissions limit the kinds of actions a helper may take; they do not automatically set a spending cap. The activation was reported by XRPL Dashboard, which tracks the network’s amendment process.
For a business, this could mean allowing one account to handle payments and another to carry out compliance-related tasks without giving either account broad control over the primary account. For example, the source report describes a stablecoin issuer authorizing a compliance account to approve new customers while keeping its main keys offline. That is an example of a possible use, not evidence that any particular institution has adopted the feature.
The warning concerns PaymentBurn, a permission intended to let a helper destroy issued tokens. Official guidance says that, under certain conditions, it can also allow a helper to create issued tokens. The issue concerns tokens issued on the ledger, not newly minted XRP. The other granular permissions are not affected, according to the report.
On-Ledger Separation of Duties
The amendment gives organizations a way to apply role-based controls directly to ledger accounts rather than relying only on internal procedures. Banks and stablecoin issuers commonly divide responsibilities among staff; delegating narrowly defined actions could make some of those divisions enforceable in transaction permissions. It may also reduce the need to keep a broadly capable primary key available on an internet-connected system for routine operations.
That design does not remove security risk. A delegated account can still perform every action granted to it, and the permissions described are not spending limits. Organizations would need to choose permissions carefully, protect each helper’s keys and review or revoke access when roles change. The PaymentBurn warning also shows that the new controls have a specific limitation while its separate fix awaits approval.
The ledger had 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 from XRP treasury company Evernorth shared with CoinDesk. Those figures provide a measure of activity in the market segments that could use account controls; they do not establish that the new feature caused those balances or that all assets involved use delegation.
As an affiliate, we earn on qualifying purchases.
How the Amendment Won Approval
XRP Ledger amendments require support from more than 80% of trusted validators for two consecutive weeks. With a list of 35 validators, that threshold means at least 29 supporters. CoinDesk reported that the delegation amendment’s countdown reset in September after support fell below the required level, before the feature activated on Oct. 8.
The activation followed a governance process, but another technical issue is still being examined. A report filed Oct. 8 said some servers may stop counting a validator after it changes a routine security key, even if the validator remains online and continues voting. A proposed patch would identify validators by permanent ID rather than by the changing key. It remains under review, so the report does not establish that the patch has been adopted.
The PaymentBurn correction is a separate amendment from PermissionDelegationV1_1. Its progress should not be confused with activation of the broader delegation feature: the delegation amendment is active, while the warning on PaymentBurn remains until the correction clears the required process and takes effect.
“The XRP Ledger held an average of $3.72 billion in tokenized assets and $539 million in RLUSD during the second quarter.”
— Evernorth, in a report shared with CoinDesk
As an affiliate, we earn on qualifying purchases.
PaymentBurn and Validator Fixes
The exact conditions that could allow a PaymentBurn delegate to create issued tokens are not detailed in the source material. The separate fix had 27 of 35 validator votes on Friday, two short of the 29 needed to begin its two-week approval countdown. The date meant by “Friday” is not specified in the report excerpt, so the vote count should be read as a snapshot rather than a current tally.
It is also unclear when the PaymentBurn correction will reach the required threshold or become active. The proposed validator-counting patch remains under review, and the material does not say when a decision or deployment is expected. No adoption figures are provided for banks or stablecoin issuers using PermissionDelegationV1_1.
As an affiliate, we earn on qualifying purchases.
Watch the Separate Fix Votes
The next measurable step for PaymentBurn is reaching at least 29 validator votes to start the required two-week countdown. Users are advised to avoid delegating that permission until the separate correction activates. The report does not provide a schedule for when that may happen.
Developers are also reviewing the proposed change to how servers identify validators during amendment voting. Further reporting would be needed to confirm whether that patch is accepted and deployed, and whether institutions begin using delegated permissions in production. Until then, the confirmed development is the activation of task-specific delegation, alongside an ongoing restriction for PaymentBurn.
blockchain account management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did the XRP Ledger activate?
It activated PermissionDelegationV1_1 on Oct. 8, 2026. The feature lets an account owner authorize another account to perform selected actions without sharing the owner’s primary keys.
Can a delegated account spend without limits?
The permissions restrict the types of actions a helper may perform, but they do not automatically impose a spending cap. An owner can grant up to 10 permissions to a helper and can change or withdraw them.
Why should users avoid PaymentBurn?
Official guidance warns that, under certain conditions, a helper with PaymentBurn permission may be able to create issued tokens rather than only destroy them. The warning concerns issued tokens, not newly minted XRP, and remains until a separate fix activates.
Has the PaymentBurn fix been approved?
Not according to the reported vote snapshot. It had 27 of the 35 validator votes on Friday, while 29 are needed to start the two-week approval countdown. The report does not specify the calendar date for that snapshot.
Are banks or stablecoin issuers already using the feature?
The source material describes possible uses, such as separating compliance and payment duties, but gives no adoption figures or examples of institutions already using PermissionDelegationV1_1.
Source: rss
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
