The XRP Ledger switched on PermissionDelegationV1_1 on Oct. 8, adding a new way for account owners to let other accounts carry out narrowly defined tasks without exposing the primary keys that control core holdings.
The change is aimed at organizations that need to separate responsibilities across teams or systems, including banks, stablecoin issuers and tokenized fund operators. Instead of sharing one powerful account, businesses can assign specific actions to helper accounts and keep their main keys offline.
How the new delegation model works
Under the new feature, an owner account can authorize another account to perform certain ledger actions on its behalf. The delegated account uses its own keys to sign, but it is limited to the permissions it has been granted.
The model is built around action types rather than a preset spending limit. According to the source article, each helper account can receive as many as 10 permissions, and those permissions can later be changed or revoked by the owner account.
Designed for separation of duties
The upgrade is intended to support operational structures that are already common in financial institutions. Banks, for example, typically keep payment and compliance functions separate across different staff or systems.
On XRPL, delegation is meant to make that split enforceable at the protocol level. A stablecoin issuer could allow one account to approve new customers while the main account that holds critical authority remains offline, reducing the need to share sensitive keys across internal functions.
Use cases across tokenized finance
The article links the feature to several institutional use cases, including stablecoins and tokenized funds. In those settings, firms often need multiple roles to interact with the same on-chain operation while maintaining internal controls.
By limiting what a delegated account can do, the system is designed to let organizations assign discrete tasks such as customer approval or payment handling without giving a helper account unrestricted authority over the primary account.
Warning over one specific permission
Officials said users should not delegate the PaymentBurn permission yet. That permission is intended to destroy tokens, but the article says that under certain conditions it could allow a helper account to create new tokens until a separate fix is activated.
The warning applies to that specific permission rather than the broader delegation framework. Other granular permissions were described as unaffected, but the advised next step is to wait for the additional fix before using PaymentBurn in delegated setups.
Source: www.coindesk.com