The XRP Ledger deployed a mechanism late Thursday that allows an account proprietor to grant another account authorization for specific functions without transferring the core private keys.
This capability, known as PermissionDelegationV1_1, went live on October 8 according to tracking platform XRPL Dashboard. Protocol updates demand more than 80% backing from trusted validators—the network participants who validate transactions—over a consecutive two-week period. Given the current roster of 35 validators, this threshold requires a minimum of 29 affirmative votes.
The countdown for delegation restarted in September after approval levels dipped beneath that requirement, as CoinDesk reported.
Enterprises engaging in frequent digital asset transactions require signing keys available on a continuous basis, but maintaining keys with extensive privileges on a web-connected machine magnifies potential losses if that workstation suffers a breach.
A mechanism termed delegation enables organizations to partition authority according to specific roles. A stablecoin issuer can empower a compliance profile to authorize new users while keeping primary keys securely offline. The designated assistant signs transactions utilizing its own credentials, executes solely the permitted functions, and the primary owner retains the ability to modify or revoke those privileges.
Every auxiliary account can acquire a maximum of 10 permissions. These constraints define the category of operations the account can execute rather than enforcing an automatic monetary ceiling.
Traditional financial institutions already separate payment operations from regulatory compliance tasks among personnel. This update provides enterprises with a mechanism to mandate those divisions directly on the decentralized ledger. coindesk.com
The blockchain network maintained an average of $3.72 billion in tokenized assets alongside $539 million in Ripple’s RLUSD stablecoin during the second quarter, according to data provided to CoinDesk by Evernorth, an XRP treasury firm. Combined, those holdings totaled approximately $4.26 billion.
Read More: XRP Ledger retries upgrade that lets banks split payment and compliance duties
Concurrently, official guidelines instruct operators to avoid delegating the PaymentBurn capability, which is designed to enable an assistant to burn tokens, until a separate patch is implemented. Under certain circumstances, that specific permission might also permit the helper to mint new tokens. This cautionary note applies to tokens issued natively on the ledger instead of freshly minted XRP. Other detailed permissions remain fully operational.
Software engineers are also investigating a defect involving how specific XRP Ledger nodes track statistics during such voting cycles. An incident report published on Oct. 8 revealed that certain servers might exclude a validator from their tally following the rotation of a standard security key, even though the validator remains active and casting votes.
A node that loses track of two validating entities calculates consensus against 33 instead of 35, which can make a motion appear closer to ratification on that specific node’s metrics than the reality dictates. A suggested software patch would prompt servers to identify validators via a permanent identifier instead, which currently remains under evaluation.
The corrective patch addressing the PaymentBurn vulnerability secured 27 out of 35 validator votes on Friday. It requires 29 votes to initiate the requisite two-week observation window that would lift the advisory warning.
Originally published at https://www.coindesk.com/tech/2026/10/09/xrp-ledger-adds-new-controls-for-banks-stablecoins-and-tokenized-funds.
