XRPL (XRP Ledger) withdrew its Permission Delegation amendment, known as XLS-75, after a bug bounty report identified a high-risk vulnerability before the feature reached mainnet. The original V1.0 implementation allowed one account to grant another narrowly defined powers, but a delegate could delete and recreate its account while retaining permissions that the original account could no longer revoke. RippleX head of engineering J. Ayo Akinyele said the team replaced V1.0 with a separately hardened V1.1 rather than patching it in place. The new version addresses delegate-identity edge cases, prevents newer Vault and Lending capabilities from being delegated unintentionally, corrects reserve accounting for delegated payments, closes a multi-signing route that could bypass delegation checks, and tightens revocation behavior. A separate medium-severity unsigned integer overflow in isDelegable could misclassify a malformed permission value as a delegable transaction type, although researchers said it had no meaningful impact without delegator misbehavior. Testing included 179 dedicated delegation tests and broader checks across related XRPL features. XRP Ledger Operations said Cantina verified the fixes, while its QA team found no regressions across 5,088 tests and no open critical internal bugs at the tested commit level. Permission Delegation was introduced in May 2025, marked unsupported in September 2025, renamed PermissionDelegationV1_1 in October, and re-supported in June 2026. The capability itself remains unchanged in V1.1; the release changes the conditions under which it can be activated.