BTC $82,452 
ETH $2,490 
USDT $0.9992 
BNB $739.57 
XRP $1.39 
USDC $0.9996 
SOL $109.89 
TRX $0.3326 
FIGR_HELOC $1.03
ZEC $1,224 XRP Ledger Activates New Controls for Institutional Accounts
The amendment lets accounts delegate transaction signing to other accounts while keeping primary keys private, with one permission still under a warning.
Key takeaways
- The bar is 29 votes. The 35-member trusted validator list required 29 votes to approve the delegation change.
- Delegates cap at 10. Each delegate may hold up to 10 permissions, which the granting account can change or revoke.
- One fix sits short. fixCleanup3_4_0 held 27 of 35 validator votes, below the 29 needed to begin approval.
What happened
The XRP Ledger switched on the PermissionDelegationV1_1 amendment on Oct. 8 at ledger 107,524,865, according to XRPL Dashboard, which lists the activation at 5:29 p.m. ET. CoinCentral reported that the change targets banks, stablecoin issuers and tokenized-asset firms. Under the feature, one account can hand off transaction signing to other accounts, so a task can run without the main keys being shared.
A delegate can hold as many as 10 permissions. The granting account can submit a fresh list to change or revoke them, and any permission left off that list is removed. Account owners authorize another account for selected transactions, and the second account signs with its own keys. Access can be changed or withdrawn without replacing credentials.
Official documentation carries a caution against delegating the PaymentBurn permission until the fixCleanup3_4_0 amendment is enabled. XRPL Dashboard showed fixCleanup3_4_0 at 27 of 35 trusted validators, two short of the 29 it lists as the requirement. Amendments that reach the majority threshold then enter a 14-day countdown before they activate.
Why it matters
CoinCentral reported the upgrade lets payment teams process authorized transactions while treasury teams keep control of primary keys. Compliance staff can receive different permissions based on assigned duties. The rules define which actions are allowed, but they do not automatically cap spending, so businesses must still apply payment limits and approval checks.
CoinCentral tied the change to new RLUSD treasury activity, including a reported 30 million token mint on October 6. 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.
What the data shows
Validators approved the change after maintaining more than 80% support for two weeks, and the 35-member trusted list required 29 votes. XRPL Dashboard lists 95 amendments live on mainnet, and it projected that fixBatchV1_2 and BatchV1_1 could activate later Friday, at 14:12 and 14:46 UTC.
What is still unclear
- Version 3.4.1 has a counting problem, per an Oct. 8 report on the rippled GitHub repository: once a validator rotates its signing key, the software no longer counts its amendment votes and drops it from the threshold calculation. After three validators rotated keys, the reporter's node showed 33 validations and a threshold of 26, rather than 35 and 28. No amendment's pass-or-fail outcome differs at present, the reporter added, and a proposed patch that would identify validators by a permanent node ID remained open for review on Friday.
- Separate work on programmable escrow is not part of the delegation upgrade. Developers released the ninth test version, which could require conditions before assets move, and that feature remains under testing.
- Ripple Prime added Brevan Howard as a client, extending Ripple's institutional services beyond the ledger. That brokerage arrangement operates outside this permission system and does not confirm that banks have adopted delegation.
Questions readers ask
What does PermissionDelegationV1_1 do on the XRP Ledger?
It lets one account authorize another account to send transactions on its behalf, so a task can be handed off without sharing the account's own keys. A delegate can hold up to 10 permissions.
Why should users avoid delegating PaymentBurn?
The XRPL amendments page advises against delegating the PaymentBurn granular permission until fixCleanup3_4_0 is enabled. Before that fix, a delegate with PaymentBurn may be able to create new trust line tokens or multi-purpose tokens as well as destroy existing ones.
How close is the fixCleanup3_4_0 amendment to approval?
XRPL Dashboard showed it at 27 of 35 trusted validators, two short of the 29 it lists as the requirement. Amendments that reach the majority threshold then enter a 14-day countdown.
How many amendments are live on the XRP Ledger mainnet?
XRPL Dashboard lists 95 amendments live on mainnet. It also projected that fixBatchV1_2 and BatchV1_1 could activate later Friday, at 14:12 and 14:46 UTC.
