The XRP community is abuzz with discussions about the upcoming activation of the Permission Delegation amendment. Data from XRPScan indicates that PermissionDelegationV1_1, scheduled to commence its two-week activation phase, received 29 approval votes on September 21, 2026. Should the current levels of support persist, this change could be implemented as early as October 5, 2026, at 11:18 UTC.
Why is Sustained Support Crucial?
For the amendment to take effect, validator support must consistently remain above 80%. If the support level drops to or below this threshold, the proposal will be rejected, resetting the 14-day activation counter.
What Does Permission Delegation V1_1 Entail?
This amendment is included in the xrpld 3.3.0 release package, addressing a significant flaw identified in the initial implementation of Permission Delegation. It aligns with the technical standard known as XLS 75.
Lauren Berta highlights that the Permission Delegation feature could unlock crucial capabilities for institutions issuing regulated assets on the XRPL, emphasizing its importance for RLUSD and other regulated tokens on the ledger.
Permission Delegation allows an account to delegate specific authority to other accounts. This feature could be particularly beneficial for institutions issuing regulated digital assets, enabling them to distribute operations across different teams. Consequently, asset movements, compliance procedures, and security management can be handled by separate accounts, safeguarding the issuer account.
Ripple‘s stablecoin product leader, Lauren Berta, states that this feature can provide a native protocol-level operational model for RLUSD on the XRPL. Known as Ripple’s USD-backed stablecoin, the RLUSD team is conducting parallel development and testing in a devnet environment.
Also known as Vet, Hussein Zangana deems the Permission Delegation structure an essential compliance and operational component for corporations. This approach is poised to be functional for asset managers offering on-chain regulated instruments and issuers tokenizing real-world assets.
Will Issuer Control Be Maintained?
The system ensures delegated authority does not equate to relinquishing full control. Certain account-level permissions remain non-transferable, preventing authorized accounts from expanding their access. The issuer account dictates which permissions are granted, with the option to revoke them instantly.
Mayukha Vadari, a software engineer at RippleX, suggests retail users might find value in this application. Users may delegate responsibilities from blackholed issuer accounts to another user-controlled account, thus maintaining control over specific settings like account domains post-closure.
Mayukha Vadari states that transferring specific functions to a separate account before a blackhole operation ensures users retain control over some settings even after account closure.
Another date on the XRP community’s radar is the Ripple Swell event, slated for October 27-29, 2026.
