XRP Ledger Nodes Stall While Validators Race Ahead

Ripple’s XRP Ledger is running on two different clocks right now. Validators have overwhelmingly embraced the network’s newest software, xrpld v3.2.0, clearing the bar with room to spare. But less than half of all nodes have followed, and a key security fix bundled with the upgrade remains stuck far below the votes it needs to switch on.

Validators Surge Ahead While Nodes Lag Behind

Ripple shipped xrpld v3.2.0 on June 15, renaming the network’s core server software from rippled to xrpld under a proposal called XLS-0095. Nearly a month later, XRPScan data shows only 357 of roughly 828 total XRP Ledger nodes, about 43%, have made the switch. Another 426 nodes, or 51%, are still running the older v3.1.3 build.

The validator picture looks completely different. Of the 35 validators on the network’s default Unique Node List, known as the UNL, 31 have already moved to v3.2.0. That works out to 89%, comfortably clearing the 80% support the network needs before any upgrade can take hold.

This is not a sign of a failed rollout. It reflects how XRP Ledger governance actually works. A small, trusted group of validators decides whether the network moves forward, while thousands of ordinary nodes simply follow their lead once that threshold is met.

Node operators who have not yet made the jump are not breaking any rule. But they are running on borrowed time. The software they are avoiding brings real gains, including a 30% to 40% cut in memory usage for full servers.

Inside The Security Fix Still Stuck In Limbo

Bundled inside v3.2.0 is a separate on chain amendment called fixCleanup3_2_0. Unlike the software itself, amendments need their own dedicated vote from validators before they activate. As of this week, only 17 of 35 UNL validators, or 48.57%, have voted yes.

That leaves the amendment well short of the 28 votes, or 80%, it needs to pass. Even after crossing that line, support has to hold steady for a full 14 days before the change becomes permanent. Any dip below that mark resets the countdown to zero.

The fixes packed into this amendment are not cosmetic tweaks. They target some of the ledger’s newest and most sensitive financial tools, the same ones institutions have been watching closely.

• Single Asset Vaults, fixing rounding and precision errors in how funds are pooled
• The native Lending Protocol, patching risks tied to borrowing against pooled collateral
• Permissioned decentralized exchanges, closing gaps flagged during security testing
• Multi Purpose Tokens, correcting how the ledger handles issuance and transfers
• Permissioned domains, tightening rules used for compliance driven applications
• New invariant checks that stop deleted accounts from leaving stray data behind

Ripple has already voted in favor of the amendment. The Lending Protocol at the center of it passed a fresh security review from Halborn in June.

That review followed a public $200,000 bug bounty months earlier, which had already caught a hidden collateral loophole and a spam risk in loan payments. Both were fixed before the feature reached mainnet.

What An Amendment Block Really Means For Users

Everyday XRP holders have nothing to worry about here. The real risk falls on node operators, exchanges and developers who run the network’s infrastructure, not on people simply holding the token.

If fixCleanup3_2_0 eventually crosses 80% and holds there, any server still running old software becomes what the XRP Ledger calls amendment blocked. In plain terms, that server gets cut off from validating new transactions until it catches up.

Quick explainer: an amendment blocked node is a server that falls out of step once a rule change goes live. It can no longer read the network correctly, and it loses its working connection to the rest of the ledger until the operator installs the update.

This is not the network’s first brush with this exact drama. Back in May, a similar deadline hit version 3.1.3. XRPL Foundation community director Hussein Zangana, known online as Vet, warned that only about 40% of nodes had updated a week before that activation window closed.

Developers are also tracking a separate migration bug tied to this rollout. A report filed as GitHub issue 7581 found a mismatch during migration. Some validators show a fresh key in their service logs, while the actual server keeps running on the old key stored in its wallet file.

Ripple’s Own Architect Puts The Upgrade To The Test

David Schwartz, Ripple’s CTO emeritus and one of three people who built the XRP Ledger back in 2012, did not sit on the sidelines during this rollout. He took his personal hub server offline to install v3.2.0 himself, treating his own infrastructure as the first test case.

He expected roughly ten minutes of downtime, but the upgrade took closer to 18 minutes since the server needed extra time to shut down safely. Schwartz later pointed to a full month of stable performance data. He flagged just one unusual stretch of peer disconnections, tied to a local network issue rather than the ledger itself.

The rename from rippled to xrpld carries weight well beyond a simple file name change. It strips a direct reference to Ripple the company out of software that XRP Ledger supporters have long insisted runs independently of any single business.

The timing lines up with other signs of momentum across the ecosystem. Ripple backed startup t54.ai just launched an XRPL AI Hub for developers and payment agents. The launch came days after the ledger quietly crossed 1 million automated agent payments processed through a system called x402.

XRP Price Holds Steady Amid Bigger Market Questions

None of this upgrade drama has rattled XRP’s price much. The token was trading near $1.09 this week, down about 3.5% over 24 hours, with daily trading volume close to $1.54 billion and a market cap around $68 billion.

XRP has spent recent weeks stuck in a tight band between roughly $1 and $1.20, waiting on bigger catalysts than a server rename. Spot XRP ETFs have logged multiple straight weeks of net inflows, pulling in close to $1.49 billion since launch. Tokenized real world assets on the ledger have also climbed past $4 billion across more than 500 products.

Traders are also watching Washington closely. The CLARITY Act, a bill that would settle XRP’s legal status as a commodity, missed its early July target and now points toward a Senate hearing on July 17. Ripple separately picked up a full MiCA license in Europe last week, giving it a clear regulatory path across 30 countries.

None of those headlines will matter much if the network’s own plumbing stays split down the middle. For now, XRP Ledger runs on two timelines at once. One is nearly finished for validators who already made the leap, while the other has barely started for the fix meant to protect the newest tools.

XRP Ledger has weathered plenty of bumpy upgrades before, and this one looks far from a crisis. But the gap between validators sprinting ahead and nodes dragging their feet is a reminder that decentralization only works when everyone actually shows up. The fixCleanup3_2_0 vote will decide how soon the ledger’s lending and vault tools get the protection they were promised. Every day it waits is a day those fixes sit unused on a live network. What do you think, should XRP Ledger set a hard deadline for lagging nodes, or is patience part of how decentralization works? Share your thoughts in the comments and pass this along to anyone who holds or builds on XRP.