The XRP Community has a big date ahead of it as the Permission Delegation amendment is getting closer to activation, with the upgrade set to go live on October 5.
Gaining 29 Yes votes, PermissionDelegationV1_1 entered a two-week activation window on September 21, 2026. Starting from this date, the earliest activation of the Permission Delegation feature will be in the next 13 days on October 5, 2026, at 11:18 AM UTC, according to XRPScan data.
This marks the earliest possible activation date, as validator support for the Permission Delegation amendment must stay above 80% the whole way. If it slips to 80% or lower even once, the amendment is rejected, and the 14-day timer starts over.
Permission Delegation allows accounts to delegate some permissions to other accounts. PermissionDelegationV1_1, bundled in the xrpld version 3.3.0, replaces Permission Delegation, fixing a critical bug discovered in the original implementation of the feature. Standard: XLS-75.
You Might Also Like
The XRP community is also looking ahead to the Ripple Swell event, scheduled for October 27 to 29, 2026.
Permission Delegation: “Big enabler for institutions”
According to Hussein Zangana (Vet), the Permission Delegation feature is a big enabler for institutions, being a compliance & operations building block.
According to Ripple stablecoin product lead, Lauren Berta, Permission Delegation has the potential to unlock an important capability for institutions issuing regulated assets on XRPL and matters for RLUSD and every regulated token on the ledger.
You Might Also Like
Permission Delegation allows issuers to delegate specific actions to separate accounts while keeping the issuer account secure. Stablecoin issuers, RWA tokenizers, and asset managers bringing regulated instruments onchain all need ways to separate the teams moving assets, enforcing compliance, and managing security.
This separation of duties is how stablecoin issuers operate on other chains: different teams are responsible for different functions.
Permission Delegation will enable that same type of operational structure for RLUSD on XRPL, natively at the protocol level.
Importantly, delegation does not mean giving up control: certain account-level permissions cannot be delegated, preventing delegates from escalating their own access. The issuer maintains control over which permissions are granted and can revoke them instantly.
Berta disclosed that the RLUSD team was building and testing against the functionality on devnet in parallel, highlighting interest in the feature.
According to RippleX software engineer Mayukha Vadari, a retail-specific use case of Permission Delegation (XLS-75) is for blackholed issuers. Before blackholing their issuer accounts, users can delegate some responsibilities (like setting the account domain) to a separate account they still control. So even after blackholing, they still control a few settings.
Be the first to comment