XRP Ledger Activates Delegated Permissions for Institutional Controls

The XRP Ledger activated delegated permissions on Oct. 8, allowing banks, stablecoin issuers and asset managers to separate day-to-day account functions from control of their primary assets.

The PermissionDelegationV1_1 amendment lets an account owner assign up to 10 specific permissions to an independent account. Examples include approving new customers, executing payments and freezing designated accounts.

The delegated account uses its own key and cannot act beyond the functions assigned to it. The original account owner retains control of the permission set and can change or revoke access. The design allows institutions to keep master keys offline while maintaining operational functions that require continuous access.

The activation follows earlier TokenPost coverage of the XRP Ledger’s delegated-permissions design.

The amendment passed through the XRP Ledger’s validator-based governance process. The ledger has 35 trusted validators, and an amendment must receive more than 80% support for two consecutive weeks, requiring at least 29 votes. The approval countdown reset in September after support fell below the threshold before the amendment activated Oct. 8.

Two issues remain relevant to the feature’s use. The PaymentBurn permission was designed to let delegated accounts destroy tokens, but under certain conditions it can also enable the creation of additional issued tokens on the ledger. A patch received 27 votes Friday, two short of the threshold needed to start its two-week approval period.

Developers are also reviewing a validator-counting defect. Some servers may remove a validator from voting calculations after the validator rotates a security key, even when it remains online and continues voting. A proposed fix would identify validators through permanent IDs and remains under review.

The XRP Ledger averaged about $3.72 billion in tokenized assets during the second quarter, alongside about $539 million of Ripple-issued RLUSD stablecoin. The combined total of roughly $4.26 billion indicates the scale of assets held by potential users of the permission controls.

The PaymentBurn patch must reach the 29-vote threshold before its two-week approval period can begin.