The XRP Ledger just rolled out its most significant software update in months, and while the network’s most important validators have embraced it, a separate security fix bundled inside the upgrade is stuck in voting limbo — leaving some of the ledger’s newest features in a strange halfway state.
By Jennifer Kim | July 11, 2026
The Hook: A Network Split in Slow Motion
If you hold XRP or follow the Ripple ecosystem, here is the situation in plain terms: the XRP Ledger (XRPL) released its v3.2.0 server software on June 15, and the upgrade is designed to make the network cheaper to run, more stable, and more attractive for institutional users like banks and payment companies.
But adoption across the broader network has been uneven. According to data from XRPSCAN, roughly 43 percent of approximately 833 active nodes have upgraded to v3.2.0, while about 51 percent remain on the older v3.1.3. That might sound concerning, but here is why it is not as alarming as it appears.
The XRP Ledger does not rely on a simple majority of all nodes. It runs on a trusted set of validators known as the Unique Node List (UNL) — currently 35 validators that the network treats as its decision-makers. For a new software version to fully activate, it needs sustained support from more than 80 percent of these validators for two consecutive weeks.
And on that front, the news is good: 31 of the 35 UNL validators — about 89 percent — are already running v3.2.0, clearing the threshold the network requires. The upgrade is effectively live from a governance standpoint, even though roughly half of the network’s smaller nodes have not yet caught up.
On-Chain Evidence: What the Upgrade Actually Does
The v3.2.0 update is not just a routine patch. It lays the groundwork for several features that Ripple and the XRPL community have been building toward, including:
- Single-asset vaults — think of these as specialized savings accounts on the ledger that hold one type of asset, designed for institutional use cases.
- Permissioned decentralized exchanges — allowing select groups to trade without exposing every transaction to the public, a feature aimed at financial institutions.
- Multi-purpose tokens (MPTs) — a flexible token standard that expands what developers can build on XRPL beyond simple payments.
- A lending protocol — an on-chain system that lets users borrow against pooled funds, similar to how DeFi lending works on Ethereum but built natively into the XRP Ledger.
For regular investors, these additions matter because they make XRPL more competitive with smart contract platforms like Ethereum and Solana. The more useful the ledger becomes, the more demand there is for XRP — the native asset used for transaction fees and liquidity on the network.
The Core Conflict: The Amendment Lagging Behind
Here is where things get tricky. Bundled with the software upgrade is a separate measure called fixCleanup3_2_0. Unlike the software itself, this is a formal on-ledger vote that requires validators to approve it over a two-week period.
The amendment packages several security fixes and improvements for the new features mentioned above — the vaults, permissioned exchanges, multi-purpose tokens, and lending protocol. It also adds internal checks designed to prevent deleted accounts from leaving behind stray data on the ledger.
But fixCleanup3_2_0 is polling far lower than the software adoption rate. While 89 percent of UNL validators upgraded their software, far fewer have voted in favor of the amendment. This creates a strange situation: validators are running the new software, but the security fixes that come with it have not yet activated.
Ripple, the payments company whose founders created the XRP Ledger, has voted in favor of the amendment. But there is a real consequence to delay: validators that fail to upgrade before the amendment eventually activates risk being shut out from the ledger entirely — a state the XRPL community calls “amendment-blocked.”
Market Implications: What This Means for Your Portfolio
For XRP holders, the upgrade story is a double-edged sword. On one hand, the fact that 89 percent of UNL validators have adopted v3.2.0 shows strong institutional and developer alignment — these are the entities that matter most for network decisions, and they are clearly on board with the direction Ripple is taking.
On the other hand, the slow node adoption — only 43 percent of all nodes — suggests that smaller operators and community-run infrastructure are lagging. This is not unusual for XRPL upgrades, but it does mean the network is in a transition period where some nodes may not support the newest features yet.
The lending protocol is particularly notable. As CoinDesk reported in late June, Ripple wants institutions to be able to borrow against tokenized assets directly on XRPL. If the fixCleanup3_2_0 amendment does not pass soon, that feature and others remain in a holding pattern — technically available in the software but without the security fixes needed to operate safely at scale.
For context, XRP is the fifth-largest cryptocurrency by market capitalization and has been one of the better-performing major altcoins in recent weeks, buoyed by growing retail wallet counts and increased exchange activity. A smooth upgrade process would add to that positive momentum.
The Verdict: Patience Required, but Direction Is Clear
The XRP Ledger’s v3.2.0 upgrade is a meaningful step forward for a network that has been steadily building institutional-grade features. The validator support is there. The software works. What remains is the slower, messier process of getting every node and every amendment vote across the finish line.
If you are a long-term XRP holder, there is little reason for alarm. The network continues to function, transactions process normally, and the upgrade path is proceeding as designed — just not as quickly as some might prefer. The real risk would be if the fixCleanup3_2_0 amendment stalls indefinitely, leaving security improvements in limbo.
For now, the takeaway is this: the XRP Ledger is upgrading, the important validators are on board, and the features that could make the network more valuable are coming — but the security fixes need to catch up before anyone should celebrate.
The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments carry risk; always do your own research.
89% validator approval but the security amendment cant pass voting? whats even the point of the upgrade if the fix everyone actually needs is stuck in limbo
a security patch stuck behind feature voting is peak governance failure. just hotfix the damn thing
amendment_watcher bundling a security patch with feature amendments is the real problem. XRPL governance needs an emergency hotfix path that doesnt require the same voting cycle
89% of UNL validators approved but a security fix is stuck. that tells you the voting mechanism is broken for anything time-sensitive
43% of nodes upgraded out of 833 is not great tbh. BTC had similar adoption lag with taproot and that took months
comparing XRPL governance to BTC taproot activation is wild. completely different mechanisms but sure, the slow node upgrade rate is a real concern
taproot took months because miners had to coordinate. XRPL just needs UNL validators and 31 of 35 are already there
permissioned DEXs on XRPL could actually pull institutional volume if Ripple plays it right. banks want privacy on settlement
425 nodes still sitting on v3.1.3 three weeks after release. upgrade your stuff people
raj_validator 425 nodes still on v3.1.3 three weeks later. XRPL doesnt have the same miner incentive structure as BTC so upgrading relies on goodwill
the fact that a security fix is bundled with features and gets held up by feature voting is a design flaw in itself. split them next time
89% of UNL validators approved but a security patch is stuck in voting. that tells you the amendment process was designed for features not security. they need a separate fast-track for fixes
Emil K. a hotfix path would help but the bigger issue is nodes that cant even be reached to upgrade. 425 silent nodes is an operational problem not a governance one
425 nodes out of 833 still on old software three weeks after release. XRPL upgrade incentives are basically peer pressure since theres no mining reward structure