The XRP Ledger activated a new feature late Thursday that lets an account owner grant specific jobs to other accounts without handing over the private keys that control the main holdings. Businesses can now build functional separation directly into the ledger.
The upgrade, called PermissionDelegationV1_1, switched on Oct. 8 after hitting the network’s amendment threshold. XRPL Dashboard notes upgrades need more than 80% support from trusted validators for two straight weeks; with 35 validators on the current list, that means at least 29 supporters.
The support count had slipped below that level in September and the countdown reset. It passed cleanly this time.
Why it matters for institutions is the operational pattern behind it. Businesses that routinely sign crypto transactions need keys available through the working day. Keeping keys with broad powers on an internet-connected machine raises the damage a breach can cause. A stablecoin issuer, for example, typically needs a compliance account holding keys online to approve new customers under know-your-customer rules, while wanting the master keys that control reserves safely in cold storage.
The feature lets a stablecoin issuer allow a compliance account to approve new customers while keeping its main keys offline, per CoinDesk.
How delegation works on the ledger
Each helper account can receive up to 10 permissions. A permission restricts the type of action the helper can perform, such as approving customers or making payments. The owner can change or revoke those grants at any time.
Crucially, a delegated account operates under its own keys, not a copy of the owner’s. Compromising a helper’s device means losing only what that helper was authorized to do, not the whole account.
CoinDesk first noted the setup when the proposal was being retried in September, framing it as banks being able to put payment and compliance duties in separate hands with the split enforced on the ledger itself rather than in a policy document.
Delegation also differs from the network’s older multi-signing option. Multi-signing requires a quorum of signers to approve every transaction, which gets clumsy at scale for routine operations. Delegation lets one helper account act within a tightly defined scope, while the owner keeps veto power over the grant itself.
Numbers already on XRPL show why issuers care. The network held an average of $3.72 billion in tokenized assets and $539 million in Ripple’s RLUSD stablecoin during the second quarter, per an Evernorth report shared with CoinDesk, together about $4.26 billion.
A known caveat on one permission
XRPL’s official guidance flags PaymentBurn, a permission meant to let a helper destroy tokens. Under certain conditions a helper with that permission can also create new tokens, not just burn them. Developers are urging users not to delegate PaymentBurn until a separate fix activates.
That fix had 27 of 35 validator votes on Friday, below the 29 threshold needed to start its two-week countdown.
Other granular permissions are unaffected.
The warning concerns tokens issued on the ledger, not newly minted XRP, so ordinary XRP holders see no exposure from this bug. The practical audience is stablecoin issuers and tokenized-fund managers, the exact firms the feature targets. A workaround in the meantime: an issuer can use authorization flows that avoid needing a helper to hold PaymentBurn, or simply wait for the fix.
This kind of disclosure is typical of how XRPL ships amendments. The network activates a feature once validator support clears the bar, and any security caveats get patched through follow-up amendments running the same process. It is slower than a centralized product release cycle but it lets the ledger adjust without a hard fork under normal conditions.
A governance bug worth watching, plus one open question
A more subtle issue surfaced on Oct. 8 in a developer report. Some XRP Ledger servers appear to drop a validator from their internal count after that validator rotates a routine security key, even though the validator is still online and voting.
That can leave a server measuring support against 33 of 35 expected votes instead of 35, making a proposal look closer to passing than it really is on that node’s view.
The delegation amendment itself activated on a correct threshold, so the concern sits at the monitoring layer rather than at the ledger’s rules. Still, developers who track governance votes from server data may see slightly optimistic support numbers until a fix ships.
The bigger open question is adoption. Whether large institutions actually use helper accounts at scale on XRPL, or continue relying on multi-signing and cold storage as they have for years, will show up in issuer-loop data over the next quarter. Delegation gives them the option; it does not force the behavior.
For readers not running XRPL infrastructure, the immediate takeaway is narrower. Ordinary wallets see no change unless they deliberately set up delegation. The upgrade changes how institutions can structure duties, not how retail users send XRP.
XRP’s spot market has been largely flat around these dates, with broader crypto markets driven by interest-rate concerns and liquidation waves rather than ledger upgrades. This change matters for the network’s institutional buildout, not this week’s price action.
The amendment follows related work on XRPL this year around credentials, permissioned decentralized exchanges and lending protocols, all aimed at making the ledger usable by regulated firms. Ripple’s RLUSD custody flows, tokenized fund balances and stablecoin issuance on the ledger are the businesses that stand to benefit first, and each of them has compliance requirements that sit awkwardly with a single all-powerful signing key.
Delegation adds one more building block to that push, and like the previous ones, it will be judged by how many regulated firms actually turn it on.