Token issuers on the XRP Ledger could soon gain a new way to manage compliance without giving employees access to the issuer’s broader account controls.
Investor and Web3 expert Jake Claver explained how PermissionDelegationV1_1 could let issuers assign specific duties to separate accounts while keeping their main keys under tighter control.
The amendment had 29 of 35 validators voting in favor, with October 8 marking the earliest possible activation date. However, one validator changing its vote could reset the approval period.
Issuers Currently Control Every Action
Claver explained in his tweet that an issuer currently uses one account to manage trust lines, freeze flagged holders, mint supply, and burn tokens. The issuer’s keys authorize each action.
That structure creates problems when companies assign compliance duties to employees. A regular key gives an employee broad authority because the key can perform the same actions as the master key. An employee who approves trust lines could also move the issuer’s XRP or change account settings.
Multi-signing provides another option, but it requires several people to approve transactions. Claver noted that this process can slow routine compliance work when employees need to approve many trust lines during a busy day.
PermissionDelegationV1_1 introduces a third approach.
The $XRP Ledger could soon let your compliance team freeze a flagged holder without the issuer's keys
29 of 35 validators vote yes and the earliest activation is Oct 8, but one vote could still push that date back
1/25🧵
— Jake Claver, QFOP (@beyond_broke) September 30, 2026
Delegates Can Handle Specific Responsibilities
The owner can use a DelegateSet transaction to assign one delegate account and up to 10 permissions. The delegate then uses its own keys to sign approved actions, while the transaction applies to the owner’s account.
Claver focused on the amendment’s granular permissions. Issuers can assign trustline authorization, freezing and unfreezing duties to compliance accounts. Treasury teams can receive PaymentMint and PaymentBurn permissions, although Claver noted that burn requires the fixCleanup3_4_0 amendment. Other permissions cover Multi-Purpose Token locking and unlocking and specific AccountSet fields such as domain, email hash, message key, transfer rate, and tick size.
For example, a stablecoin issuer could give its compliance team three trust line permissions while giving its treasury team PaymentMint authority. An operations employee could receive permission to update the company’s domain.
Those delegates could not move the issuer’s XRP or change its keys. If an employee leaves the company, the issuer can remove that person’s permissions through another DelegateSet transaction without rotating the issuer’s main keys.
Earlier Version Raised A Security Issue
Claver also described how developers tested the feature before reaching the current version. On September 15, 2025, a community developer identified an issue with the original PermissionDelegation implementation. The permission check came before the signature check, which could let someone submit an unauthorized transaction with a high fee and make the account pay despite the failed action.
Validators rejected that version, and the revised implementation now returns terNO_DELEGATE_PERMISSION when an account lacks the required permission. That result does not charge the account a transaction fee.
Claver also noted that BatchV1_1 went through a similar revision process, while an emergency xrpld 3.4.1 release introduced fixBatchV1_2.
We are on X, follow us to connect with us :- @TimesTabloid1
— TimesTabloid (@TimesTabloid1) June 15, 2025
Validator Support Determines The Timeline
Claver connected the proposed feature to the growing activity on the XRP Ledger. He cited approximately $1.1 billion in RLUSD issued on the ledger as of September 28 and around $4.1 billion in tokenized real-world assets tracked by rwa.xyz.
The amendment needs more than 80% validator support for two consecutive weeks. With 35 validators, 29 votes would pass the amendment. PermissionDelegationV1_1 had exactly 29 votes when Claver published his assessment, meaning one validator could push the activation date back.
Claver said issuers should map their compliance responsibilities before October 8 and determine which duties they want delegates to handle while keeping broader authority with the issuer.
Disclaimer: This content is meant to inform and should not be considered financial advice. The views expressed in this article may include the author’s personal opinions and do not represent Times Tabloid’s opinion. Readers are advised to conduct thorough research before making any investment decisions. Any action taken by the reader is strictly at their own risk. Times Tabloid is not responsible for any financial losses.
Follow us on X, Facebook, Telegram, and Google News
