XRP rallies 17% while XRPL amendment gains support

XRP has climbed 17% to an intraday high of $1.43 as Ripple’s vote for the PermissionDelegationV1_1 amendment has moved a key part of the XRP Ledger’s version 3.3.0 upgrade deeper into the validator approval process.

XRP Ledger amendment has entered its validator vote

XRPL validator voting data showed that seven of the 35 validators on the default Unique Node List supported PermissionDelegationV1_1 at the latest count. Ripple’s affirmative vote adds support from one of the network’s most closely watched participants, but it does not approve or activate the feature.

Under the XRP Ledger’s amendment process, a proposal must retain support from more than 80% of trusted validators for two continuous weeks. Based on the current 35-validator configuration, PermissionDelegationV1_1 would need at least 29 votes to exceed 80%, though some community trackers describe the practical threshold as 28 of 35.

If support falls to 80% or lower during the two-week window, the waiting period restarts. Validators can also change their votes before an amendment becomes active, leaving the activation date dependent on the network rather than Ripple alone.

PermissionDelegationV1_1 would let an XRP Ledger account authorize a second account to carry out selected transaction types. The account owner could grant narrowly defined permissions without transferring full signing authority or control of every account function.

Such an arrangement resembles role-based access systems used by financial companies, where employees and service providers receive access only to the operations required for their work. A business could, for example, let one account handle an approved transaction category while keeping control over unrelated payments and account settings.

RippleX head of product Jazzi Cooper linked the feature to controls needed by regulated financial institutions that issue and manage assets on public blockchains.

“Tokens are the pre-requisite for on-chain utility; you can’t move value without it existing on-chain first,” Cooper said.

In the rest of her statement, Cooper said regulated institutions need suitable controls before they can bring tokenized value onto a public ledger. Permission Delegation is designed to provide part of that account-level structure.

PermissionDelegationV1_1 replaces an earlier version

The XRP Ledger’s official amendment registry says PermissionDelegationV1_1 replaces the original PermissionDelegation proposal, which was disabled in version 2.6.1 after developers identified a critical bug.

The revised amendment, based on the XLS-75 specification, keeps the limited-authority model while correcting the flaw found in the earlier implementation. Security work has carried added weight because the feature would determine which transactions another account can submit on behalf of an owner.

Released in August, XRP Ledger version 3.3.0 introduced PermissionDelegationV1_1 alongside BatchV1_1, ConfidentialTransfer, DynamicMPT, Sponsor, and the fixCleanup3_3_0 package. An earlier XRPL upgrade report detailed how the proposals cover atomic transaction batches, private token transfers, adjustable token properties, and sponsored network costs.

ConfidentialTransfer would allow users to conceal Multi-Purpose Token balances and transfer amounts while leaving the sending and receiving accounts visible. DynamicMPT would let issuers change selected token properties after issuance, while Sponsor would allow a third party to cover reserve requirements and transaction fees for another account.

BatchV1_1 would group several transactions so they succeed or fail under defined conditions. Such processing can support settlement workflows in which several related actions must be completed together rather than separately.

Node operators need software containing the code for an approved amendment before it activates. According to XRPL documentation, servers using older software become amendment-blocked when they encounter protocol rules they cannot understand, preventing them from processing ledger data under outdated assumptions.

The fixCleanup3_3_0 amendment packages corrections involving Single Asset Vaults, the Lending Protocol, automated market makers, permissioned exchange functions, Checks, and pseudo-accounts. Ripple also backed the fixes during their validator vote.

XRP Ledger lending proposals remain below activation level

Permission Delegation is advancing through the same governance system as the proposed Single Asset Vault and Lending Protocol amendments, both of which have already received Ripple’s support.

Single Asset Vaults, described in XLS-65, would allow several depositors to pool one type of asset, including XRP, RLUSD, or another token issued on the ledger. Depositors would receive vault shares representing their proportional interest in the pooled assets.

XLS-66 would add fixed-term lending functions at the ledger level, including loan issuance, servicing, and repayment. The design uses pooled vault liquidity and off-chain credit assessment rather than requiring every loan to be secured by excess crypto collateral.

Recent validator voting coverage reported support of about 40% for Single Asset Vaults and more than 37% for the Lending Protocol after Ripple voted in favor. Both totals remained well short of the required supermajority.

A June re-audit by blockchain security firm Halborn found no critical or high-severity issues in the lending code it reviewed. Formal verification work involving RippleX and protocol research firm Common Prefix has also tested whether the system could enter unintended states that ordinary scenario-based reviews might miss.

For U.S. users, the protocol votes do not change the legal status of XRP, RLUSD, tokenized securities, or lending products. Any American company using the functions would remain responsible for the federal and state rules that apply to its product, while validator approval would only determine whether the underlying XRPL features become available.

XRP gains as ETF and futures activity increases

Against the upgrade vote, XRP rose more than 17% over 24 hours to reach $1.43, its highest price of the day. The token advanced about 40% over seven days after trading as low as $1.22 during the latest session, while spot trading volume increased 156%.

The token’s rise also formed part of a strong crypto market rebound that produced heavy short liquidations. As traders who had bet on lower prices bought assets to close leveraged positions, XRP moved through several resistance levels during the session.

U.S. spot XRP exchange-traded funds recorded $13.24 million in net inflows on Thursday, according to SoSoValue data. Bitwise’s fund accounted for $9.9 million, while Franklin Templeton’s product received another $3.34 million.

ETF shares give U.S. investors regulated brokerage exposure to XRP without requiring them to hold the token directly. Flows into the products do not measure demand across the entire spot market, but daily creations and redemptions provide a separate view of activity in U.S.-listed investment vehicles.

Derivatives positioning rose alongside the spot price. CoinGlass data cited in the report put total XRP futures open interest at $3.44 billion, up more than 17% over 24 hours.

CME-listed XRP futures open interest increased by more than 35% during the same period, while Binance recorded a 15% rise and Hyperliquid posted a 29% increase. Open interest measures the value of outstanding contracts and can rise when traders add either long or short exposure; by itself, the figure does not establish which side controls the market.