XRP Ledger activated PermissionDelegationV1_1 on Oct. 8, allowing account owners to authorize other accounts to perform specific tasks without giving up the primary key that controls the account.
Validator threshold and earlier reset
According to monitoring site XRPL Dashboard, this type of amendment requires backing from more than 80% of trusted validators for two consecutive weeks. Based on the current validator count of 35, at least 29 approvals were needed.
The countdown for the amendment had been reset in September after support dropped below the required threshold.
How the delegation model works
The feature lets enterprises split permissions by function. Stablecoin issuers can authorize compliance accounts to approve new customers while keeping the primary key offline.
Delegated accounts sign with their own keys and can carry out only the operations they were granted. The owner can change or revoke those permissions at any time. Each delegated account can receive up to 10 permissions. Those permissions limit the types of actions the account can take, rather than automatically setting spending caps.
Banks had already separated payment and compliance duties at the employee level. With this amendment, that division can now be enforced at the ledger level.
Tokenized asset figures and official warning
According to a report shared with CoinDesk by XRP treasury company Evernorth, the network held an average of $3.72 billion in tokenized assets and $539 million in Ripple’s RLUSD stablecoin during the second quarter, for a combined total of about $4.26 billion.
Official guidance says users should not delegate the PaymentBurn permission until a separate fix is activated. That permission was intended to let an assistant burn tokens, but under some conditions it can also allow the creation of new tokens. The warning applies to tokens issued on the ledger, not newly minted XRP.