XRP Ledger Activates Permission Controls for Institutional Accounts
Key Takeaways
- •The XRP Ledger activated the PermissionDelegationV1_1 amendment on October 8, allowing account owners to delegate selected transaction permissions without sharing primary private keys.
- •Each delegated account may hold up to 10 permissions, but the rules do not automatically cap spending, so businesses must apply their own payment limits and approval checks.
- •Validators approved the amendment after it maintained more than 80% support for two weeks, meeting the 29-vote threshold on the ledger's 35-member trusted validator list.
- •Official documentation warns against delegating the PaymentBurn permission, as a known flaw could let an authorized account create issued tokens rather than only destroying them.
- •The fixCleanup3_4_0 amendment proposed to fix that flaw held 27 of 35 validator votes on Friday, two short of the 29 needed to begin its approval period.

The XRP Ledger activated its PermissionDelegationV1_1 amendment on October 8, allowing businesses to assign account permissions to other accounts without sharing their primary private keys. The upgrade is designed for banks, stablecoin issuers, and tokenized-asset firms that need to delegate day-to-day operations while keeping main signing keys secure. Because a primary key grants unrestricted control over an account, operators have traditionally faced a trade-off between distributing daily tasks and keeping master credentials isolated.
Delegated Access Without Key Sharing
Under the new system, an account owner can authorize another account to carry out selected transaction types. The delegate signs those transactions with its own keys, and the owner can modify or revoke access at any time without replacing credentials. That revocability is what separates delegation from circulating a key, which cannot be un-shared once copied.
Each delegated account may hold up to 10 permissions. These rules define which actions are allowed but do not automatically cap spending. Businesses must still apply their own payment limits and approval checks on top of any delegated access.
Broader Institutional Tooling on the Ledger
An October 6 Smart Escrow testing update described a parallel development: developers released the ninth test version of programmable escrow, a feature that could require specified conditions to be met before assets move. That functionality remains under testing and operates separately from the delegation upgrade.
The delegation upgrade opens expanded institutional workflows: payment teams can process authorized transactions while treasury staff retain control of primary keys, and compliance personnel can receive permissions scoped to their assigned duties. The model mirrors the segregation-of-duties controls that traditional treasury and compliance teams already apply outside crypto.
Validators approved the delegation amendment after it maintained more than 80% support for two weeks, according to the XRPL amendments dashboard. The ledger's 35-member trusted validator list required 29 votes, and the approval count restarted in September after support fell — a reminder that amendment support is measured continuously, not captured in a single vote.
Stablecoin Activity and Token Controls
The activation follows fresh RLUSD treasury activity, including a reported 30 million token mint on October 6. Issuers can now use separate accounts for permitted tasks without exposing their main credentials.
Evernorth reported average second-quarter balances of $3.72 billion in tokenized assets and $539 million in RLUSD on the network. Those figures describe recorded on-ledger activity, not adoption of the new delegation feature.
Official documentation warns users not to delegate the PaymentBurn permission yet. A known flaw can, in some circumstances, let an authorized account create issued tokens instead of only destroying them. The warning does not concern new XRP. That caution remains in effect while the corresponding fix works through the amendment process.
Security Fix and Validator Review
Developers proposed the fixCleanup3_4_0 amendment to address that flaw. It held 27 of 35 validator votes on Friday, below the 29 needed to begin its approval period. The two-vote gap is the nearest checkpoint to watch, with support tracked on the same amendments dashboard; reaching 29 votes would start the two-week approval clock that delegation already completed.
Separately, Ripple Prime added Brevan Howard as a client, extending Ripple's institutional services beyond the ledger itself. The brokerage arrangement operates outside the new permission system and does not confirm that banks have adopted delegation.
A server issue may miscount validators after routine key changes. Developers are reviewing a patch that would identify validators through permanent IDs rather than changeable keys. The fix amendment faces the same validator-consensus bar that delegation cleared: sustained support above the 80% threshold.
Source: CoinCentral