Headline: XRP jumps 17% as Ripple backs XRPL “Permission Delegation” amendment — what it means for institutions and markets XRP spiked as much as 17% to an intraday high of $1.43 after Ripple cast a validator vote for PermissionDelegationV1_1, one of the key proposals in the XRP Ledger’s v3.3.0 upgrade. The vote pushed the amendment further into the XRPL’s governance process and helped fuel a broader market rebound that included heavy short-liquidations and increased trading volumes. Where PermissionDelegation stands in the vote - At the latest count, 7 of the 35 validators on the default Unique Node List (UNL) had signaled support for PermissionDelegationV1_1 — including Ripple’s validator. Ripple’s vote is influential but does not by itself enable the feature. - To activate, an XRPL amendment must hold support from more than 80% of trusted validators for two continuous weeks. Under the current 35-validator configuration that means roughly 29 votes (some trackers put the practical threshold at 28 of 35). - If support slips to 80% or below during the two-week window, the waiting period restarts. Validators can also change votes before activation, so timing depends on the network as a whole, not any single participant. What Permission Delegation would do PermissionDelegationV1_1 would let an account delegate narrowly defined authority to a second account — allowing that delegated account to submit only certain transaction types on behalf of the owner. The model provides limited, role-based access rather than full signing control. Why that matters: it mirrors corporate access controls used by banks and custodians. A business could, for example, permit a separate account to execute predefined token transfers while preserving control over other payments and account settings. Jazzi Cooper, head of product at RippleX, has said features like this are part of the control layer institutions need before they’ll move regulated tokenized assets onto public ledgers. Background and security fixes - PermissionDelegationV1_1 replaces an earlier PermissionDelegation proposal that was disabled in version 2.6.1 after developers discovered a critical bug. The revised amendment follows the XLS-75 specification and corrects the prior flaw. - The security work is significant because the amendment determines which transactions a delegated account may submit on behalf of another account. Other proposals packaged in XRPL v3.3.0 Released in August, version 3.3.0 bundled several amendments that expand XRPL functionality: - BatchV1_1: atomic transaction batches that succeed or fail together, useful for multi-step settlement workflows. - ConfidentialTransfer: hides Multi‑Purpose Token balances and transfer amounts while keeping sender/receiver addresses visible. - DynamicMPT: lets token issuers change selected properties after issuance. - Sponsor: allows a third party to cover an account’s reserve requirements and transaction fees. - fixCleanup3_3_0: a package of corrections affecting Single Asset Vaults, the Lending Protocol, AMMs, permissioned exchange functions, Checks, and pseudo-accounts. Operational requirements and effects Node operators must run software that includes approved amendment code before an amendment activates. Servers running older software can become “amendment-blocked” if they encounter rules they don’t understand, preventing them from processing new ledger data. Related governance items: vaults and lending Permission Delegation is progressing alongside other governance proposals that also recently drew Ripple’s support: - Single Asset Vaults (XLS-65) would let multiple depositors pool one asset type (XRP or tokens) and receive proportional vault shares. - Lending Protocol (XLS-66) would add fixed-term lending primitives at the protocol level, using pooled vault liquidity and off-chain credit checks rather than requiring overcollateralization for every loan. Current validator support reported at the time of the vote was roughly 40% for Single Asset Vaults and just over 37% for the Lending Protocol — well short of the supermajority needed for activation. A June re-audit by Halborn found no critical or high-severity issues in the lending code reviewed, and RippleX with Common Prefix have run formal verification to test for unintended states. Legal note for U.S. users Protocol votes do not change the legal or regulatory status of XRP, RLUSD, tokenized securities, or lending products in the United States. Any American company implementing these features remains subject to applicable federal and state rules; validator approval governs feature availability on the ledger, not compliance. Market reaction and flows - Price: XRP rose more than 17% over 24 hours to $1.43 (intraday high) and was up about 40% over the past seven days from recent lows near $1.22. - Volume: spot trading volume jumped roughly 156%. - ETFs: U.S. spot XRP ETFs saw net inflows of $13.24 million on Thursday (SoSoValue). Bitwise accounted for $9.9M and Franklin Templeton $3.34M. ETF creations/redemptions give a window into institutional flows in U.S.-listed vehicles but don’t capture global spot demand. - Derivatives: total XRP futures open interest climbed to about $3.44 billion (up more than 17% in 24 hours). By venue, CME-listed futures open interest rose over 35%, Binance up ~15%, and Hyperliquid up ~29%. Open interest measures outstanding contract value and can rise when traders add either long or short exposure — it doesn’t by itself indicate which side is dominant. Bottom line Ripple’s validator vote for PermissionDelegationV1_1 signals growing institutional-focused tooling on the XRPL, but the feature still needs broad validator buy-in and time to clear the amendment activation window. Meanwhile, XRP’s price surge and inflows into U.S. ETF products have amplified market momentum — a reminder that protocol governance events can ripple through markets even before amendments formally activate. Disclosure: This article is for informational purposes only and does not constitute investment advice. Read more AI-generated news on: undefined/news