The XRP Ledger activated PermissionDelegationV1_1 on October 8, 2026, enabling institutions to delegate specific permissions to secondary accounts without exposing their master signing keys. The upgrade targets banks, stablecoin issuers, and tokenized fund managers, while a separate validator vote-counting bug surfaced on the same day.
🔑 Key takeaways
- PermissionDelegationV1_1 went live on October 8, 2026
- Up to 10 permissions per helper account, revocable at any time
- Adoption requires >80% validator backing for two consecutive weeks (29/35)
- PaymentBurn patch sits at 27/35 votes, needs 29 to clear the warning
- $3.72B in tokenized assets and $539M RLUSD hosted on average in Q2 2026
Why permission delegation on the XRP Ledger
Financial institutions using blockchain face a familiar operational dilemma: signing keys (private cryptographic keys authorizing transactions) must remain hot during business hours to enable real-time settlement, but permanent internet exposure opens the network to hacking. PermissionDelegationV1_1 tackles the problem by splitting authorities by function without ever transferring control of the primary account.
In practice, a stablecoin issuer can now authorize a dedicated compliance account to run KYC verifications while master keys stay offline in an air-gapped environment. The helper signs transactions with its own keys, can only execute actions explicitly authorized by the owner, and those grants can be modified or revoked at any moment by the primary account holder.
Each helper account can receive up to 10 distinct permissions. Rather than capping spending amounts, each permission restricts the type of action allowed. For a bank, this makes the separation of duties already enforced between payment, compliance, and treasury teams executable on-chain.
Adoption process and validator threshold
For a protocol amendment to take effect, the XRP Ledger requires more than 80% of validators to maintain support for two consecutive weeks. With 35 validators currently active, the threshold translates to a minimum of 29 affirmative votes. The process was interrupted in September 2026 when backing fell below that level, as reported by CoinDesk, which reset the two-week countdown.
“The XRP Ledger governance mechanism relies on decentralized consensus: an amendment only goes live after two continuous weeks above 80% support, ensuring broad adoption before deployment.”
XRP Ledger technical documentation
| Parameter | Value |
|---|---|
| Active validators | 35 |
| Adoption threshold | 80% (29/35) |
| Required duration | 2 consecutive weeks |
| Max permissions per helper | 10 |
| Current PaymentBurn patch support | 27/35 (77%) |
The PaymentBurn bug and the vote-counting flaw
The network flagged a security issue in the PaymentBurn permission, designed to let a helper destroy issued tokens. Under certain conditions, that permission could also enable the helper to mint new tokens — a critical vulnerability for issuers. The warning applies only to tokens issued via tokenization standards on the ledger; freshly minted XRP (the native protocol asset) are not affected. Other granular permissions do not share this flaw.
Developers released a patch that had reached 27 of 35 votes by Friday. To trigger the two-week countdown that would lift the warning, the patch must reach 29 votes, the standard adoption threshold.
A separate bug was identified in how some XRP Ledger servers tally votes during amendment processes. A report filed on October 8 revealed that some servers drop a validator from their tally after a security-key rotation, even if the validator remains in operation. A server losing track of two validators would compute support over 33 instead of 35 votes, falsely suggesting the network is closer to the validation threshold. A proposed patch would have servers track them by a permanent ID rather than their current public key.
Institutional volumes and the Multi-Purpose Token standard
Tokenized assets on the XRP Ledger represent significant volumes. According to a report shared with CoinDesk by Evernorth, an XRP treasury company, the network hosted an average of $3.72 billion in tokenized assets and $539 million of Ripple’s RLUSD stablecoin during Q2 2026. In aggregate, those combined balances totaled roughly $4.26 billion.
RLUSD reached approximately $1.6 billion in market capitalization. According to 21shares, more than half of RLUSD’s total supply circulated on the XRP Ledger for the first time in mid-2026, illustrating the ledger’s growing role in stablecoin circulation for traditional asset-backed tokens.
The Multi-Purpose Token (MPT) standard enables institutions to issue real-world assets — bonds, funds, money-market shares — with compliance requirements coded directly into the token itself. Ripple’s tokenization protocol provides several key features for financial institutions:
- Programmable governance with immutable audit trails
- Automated asset lifecycle management (issuance, transfer, redemption)
- Integrated compliance controls (KYC, AML, sanctions screening) executed pre-settlement
- Freeze and clawback capabilities to reverse unauthorized transfers
- Multi-chain distribution with synchronized balances across blockchains
Over the past year, the XRP Ledger processed roughly 1.7 million transactions and settled close to $1.3 billion of on-chain value per day, for a cumulative total near $500 billion.
Conclusion: institutional adoption under control
The activation of PermissionDelegationV1_1 marks an important step toward positioning the XRP Ledger as settlement infrastructure for institutions. By enabling granular separation of duties without compromising custody of master keys, the network answers a core operational requirement of regulated banks and issuers. Resolving the PaymentBurn bug and the vote-tallying flaw quickly will nevertheless be key to maintaining validator and issuer confidence.
In the short term, two scenarios deserve close monitoring: the patch reaching the 29-vote threshold to lift the PaymentBurn warning, and the evolution of tokenized asset volumes in Q3 2026. If the upward trend in RLUSD and MPT issuance continues, the XRP Ledger could consolidate its position among the leading institutional tokenization networks, provided its technical governance remains robust.
Sources
- CoinDesk – XRP Ledger adds new controls for banks, stablecoins and tokenized funds
- Ripple – Issue Tokenized Assets
- CryptoPanic – XRP Ledger adds new controls
- 21shares – How is XRP used
This article is for informational and educational purposes only. It does not constitute investment advice. Do your own research (DYOR) before making any decision.
