Key Highlights
- The PermissionDelegationV1_1 amendment started its 14-day activation window on September 21 following approval from 29 out of 35 validators.
- Activation is scheduled for October 5 at 11:18 UTC, provided validator consensus remains at the 80% threshold.
- Account holders will gain the ability to assign limited payment and compliance responsibilities to other accounts while maintaining primary control.
- This version corrects a security vulnerability found in the original proposal related to improper transaction fee assessments.
- The xrpld 3.3.0 update modifies authorization procedures to prevent fee charges on failed transactions before signature confirmation.
The XRP Ledger stands ready to introduce granular permission controls that enable account owners to delegate specific operational tasks to trusted parties. Following strong validator backing, PermissionDelegationV1_1 launched its two-week activation timeline on September 21. With 29 validators from a pool of 35 confirming support for the proposal, the amendment meets the necessary 80% approval benchmark. The feature will become active on October 5 at 11:18 UTC, assuming sustained validator consensus throughout the countdown period.
Granular Permission Controls Transform Account Management
The amendment introduces a framework allowing primary account holders to grant targeted permissions to auxiliary accounts. Financial institutions issuing stablecoins can authorize compliance verification systems to perform customer approval functions while preserving offline key storage for security. Operational accounts receive payment execution privileges without accessing critical functions like key modification or delegate appointment capabilities.
The delegation system supports up to 10 distinct permissions per designated account, with the primary account retaining authority to modify or terminate these privileges. This framework aligns with established practices in financial institutions where payment processing, regulatory compliance, and security management operate independently. Recent developments on the XRPL platform have introduced AI-powered payment capabilities for service automation, expanding the ecosystem’s transactional functionality.
Validator Consensus Drives Amendment Timeline
The activation process requires continuous support from a minimum of 28 validators among the 35-node network throughout the countdown phase. Should approval rates drop beneath this threshold, the activation sequence restarts from the beginning. This mechanism ensures validators have adequate opportunity to assess the amendment before network implementation.
This voting cycle coincides with additional XRP Ledger enhancements progressing through the amendment pipeline. The Batch V1.1 enhancement received substantial validator backing recently, as the network continues refining transaction processing and account functionality. PermissionDelegationV1_1 introduces additional flexibility for enterprises requiring distinct operational authority structures.
Updated Version Addresses Security Vulnerability
PermissionDelegationV1_1 supersedes a previous iteration that contained a critical fee-handling vulnerability. A community security researcher identified the weakness in September 2025 during pre-deployment testing. The flaw created an exploit pathway where malicious actors could submit transactions forcing unrelated accounts to incur fees ahead of signature validation.
Development teams restructured the rejection mechanism within xrpld 3.3.0, implementing authorization verification protocols that prevent fee assessment before confirming legitimate signatures. This enhancement accompanies expanding wallet adoption, with 3,647 new wallets created during XRP’s recent price movement while developers finalized multiple amendments.
The revised amendment preserves the core delegation architecture while strengthening transaction validation procedures. Assuming validator support maintains the 80% threshold, the XRP Ledger will deploy the amendment on October 5. Account operators will then access functionality enabling them to distribute operational responsibilities across multiple accounts while consolidating primary control under segregated cryptographic keys.





