The XRP Ledger activated the PermissionDelegationV1_1 amendment on October 8, 2026, enabling account owners to assign up to 10 granular transaction permissions to third parties without sharing master signing keys. Designed for institutional use cases, developers caution against delegating the PaymentBurn action due to a token minting flaw that awaits the fixCleanup3_4_0 amendment.
PermissionDelegationV1_1 activation
- ▪PermissionDelegationV1_1 activated on the XRP Ledger after achieving two consecutive weeks of over 80% approval from trusted network validators, requiring at least 29 of 35 validator votes
- ▪PermissionDelegationV1_1 replaces an earlier version of account delegation on the XRP Ledger that was pulled after a critical bug was discovered
- ▪The XRP Ledger activated the PermissionDelegationV1_1 amendment on October 8, 2026, at ledger 107,524,865
Delegated account permissions
- ▪Under PermissionDelegationV1_1, XRP Ledger account owners can assign a delegate up to 10 granular permissions restricted by action type rather than spending limits
- ▪The PermissionDelegationV1_1 amendment allows XRP Ledger account owners to authorize third-party accounts to perform specific transactions without exposing primary signing keys
- ▪XRP Ledger account owners can modify or revoke delegated account permissions at any time by submitting an updated permissions list
PaymentBurn delegation flaw
- ▪XRP Ledger developers advised users not to delegate the PaymentBurn permission until a separate technical amendment, fixCleanup3_4_0, activates on the network
- ▪Under specific conditions, delegating the PaymentBurn permission on the XRP Ledger allows authorized delegate accounts to mint new issued tokens instead of destroying existing tokens
fixCleanup3_4_0 amendment status
- ▪The fixCleanup3_4_0 amendment on the XRP Ledger held 27 of 35 trusted validator votes on October 9, 2026, requiring 29 votes to initiate a 14-day activation countdown
- ▪An October 8, 2026 GitHub report identified a bug in rippled server software that drops validators from vote counts when signing keys rotate, miscalculating approval thresholds
XRPL tokenized asset growth
- ▪An October 7, 2026 RWA Foundation report recorded $3.7 billion in year-to-date tokenized real-world asset growth on the XRP Ledger, excluding stablecoins
- ▪RWA.xyz data from October 9, 2026 listed $4.54 billion in represented real-world assets and $499 million in distributed assets on the XRP Ledger, excluding stablecoins
Institutional custody use cases
- ▪PermissionDelegationV1_1 enables institutions on the XRP Ledger to enforce operational duties between payments, compliance, and treasury roles across separate ledger accounts
- ▪The XRP Ledger activated the BatchV1_1 amendment on October 9, 2026, at ledger 107,540,993, enabling atomic batching for linked transfers
Debatable claims
- ▪Action-type account delegation without spending caps exposes institutional funds to excessive risk
- ▪XRPL network validators should delay feature activations until related security fixes take effect
- ▪Prioritizing institutional compliance features over retail functionality best serves the XRPL ecosystem
Story comments
Loading comments…