XRP Ledger Activates New Controls for Institutional Accounts

TLDR

• XRP Ledger activated PermissionDelegationV1_1 on October 8, allowing businesses to assign account permissions without sharing private keys.
• The upgrade allows banks and stablecoin issuers to manage transactions while keeping primary account keys secure.
• Each delegated account can receive up to 10 permissions, which account owners can modify or revoke.
• XRPL developers warned against using PaymentBurn delegation until a separate fix addresses a known token creation risk.
• Developers are reviewing a validator voting issue as XRPL expands its tools for institutional financial operations.

---

The XRP Ledger activated PermissionDelegationV1_1 on October 8, allowing businesses to assign tasks without sharing their main signing keys. The change targets access for banks, stablecoin issuers, and tokenized-asset firms.

Accounts Gain Limited Access

Account owners can authorize another account to carry out selected transactions. The second account signs with its own keys. Owners can change or withdraw access without replacing credentials.

Each delegate may hold up to 10 permissions. These rules define which actions are allowed but do not automatically cap spending. Businesses must still apply payment limits and approval checks.

XRP Ledger Broadens Business Tools

An October 6 Smart Escrow testing update described another development. Developers released the ninth test version of programmable escrow, which could require conditions before assets move. That feature remains under testing.

The delegation upgrade operates separately. It lets payment teams process authorized transactions while treasury teams retain control of primary keys. Compliance staff can receive different permissions based on assigned duties.

Validators approved the change after maintaining more than 80% support for two weeks. The 35-member trusted list required 29 votes. Approval restarted in September when support fell.

Stablecoin Operations and Token Controls

The upgrade also follows new RLUSD treasury activity, including a reported 30 million token mint on October 6. Issuers can 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 activity, not adoption of the new feature.

Official documentation warns users not to delegate PaymentBurn yet. A flaw can sometimes let authorized accounts create issued tokens instead of only destroying them. The warning does not concern new XRP.

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.

Separately, Ripple Prime added Brevan Howard as a client, extending Ripple’s institutional services beyond the ledger. The brokerage arrangement operates outside this permission system and does not confirm 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.