XRP Ledger Permission Delegation Nears Mainnet Activation
In brief
- Permission Delegation lets users delegate onchain tasks while keeping account keys in cold storage
- Feature was disabled September 2025 after a bug allowed accounts to charge fees to others
- fixCleanup3_2_0 amendment with the fix achieved majority support with 30 yes votes
The Bug and the Fix
A vulnerability in the original implementation allowed an account to charge transaction fees to any other account, creating a vector for malicious actors to drain an account's XRP balance. This flaw prevented the feature from being enabled on mainnet. The bug prompted developers to pause the rollout and conduct additional security review.
Now, the fixCleanup3_2_0 amendment — a collection of fixes for Single Asset Vaults, the Lending Protocol, and the permissioned delegation framework — has achieved a majority and entered a two-week activation period with 30 yes votes. This represents a significant step toward restoring the feature to the ledger.
Why It Matters for Treasury Management
Permission Delegation was born out of the need to manage a treasury. The mechanism grants various permissions to another account to send transactions on behalf of the user's account, without exposing the primary keys. This architecture appeals to institutional operators managing large XRP holdings or complex onchain operations.
Discussions about Permission Delegation date back to 2024, reflecting the community's long-standing interest in more sophisticated access controls. The feature aligns with the XRP Ledger's growth — the network has surpassed 8 million accounts, with the total currently standing at 8,001,658 according to XRP Ledger Services.
Market activity around XRP has also shifted. Binance's XRP reserves have hit their lowest level since February this month, falling to 2.61 billion XRP, according to CryptoQuant data. The combination of institutional tooling improvements and reserve movement underscores evolving demand dynamics in the ecosystem.
