XRP Ledger’s new upgrade is here. But not everyone’s on board yet

Upgrade rollout exposes a split among validators

New software leads by validator status, not by nodes

The XRP Ledger upgrade is live in the sense that the newest client version has become the software leader among the network’s validators — yet adoption is nuanced. Multiple sources report that, while the latest release now leads by the number of validators running it, the older v3.1.3 still has a higher node count. That divergence matters because software leadership among validators doesn’t automatically equal immediate network-wide activation.

What that means for consensus and stability

When validator operators migrate at different speeds, the ledger can continue operating smoothly, but the collective decision to flip protocol behavior is delayed. For the upgrade to flip on fully, the network requires a specific activation mechanism tied to consensus thresholds, not simple version prevalence.

The 80% activation hurdle and the trusted validator list

Why 80% matters for the upgrade

The upgrade includes a safety gate: it needs 80% endorsement from the trusted validator list to activate. That threshold is intentionally high to avoid accidental protocol changes and to ensure major validators buy in before potentially disruptive behavior is enabled.

Trusted validator list vs. general node count

The trusted validator list is the set of validators that nodes and client operators rely on for canonical consensus. A high share of validators on the new software doesn’t guarantee 80% of the trusted validator list has signaled support. Thus the upgrade remains in a pending state until trusted validators — not just individual nodes — reach the activation bar.

Security amendment remains a separate, slower vote

Security amendment separated from core upgrade

The release bundles a security amendment intended to harden parts of the codebase, yet that amendment is treated separately and is progressing on a slower vote schedule. The project team emphasized that “the security risk is the part we take most seriously,” citing concerns about old code and potential AI exploit vectors.

Implications of a delayed security vote

Holding the security amendment as a distinct vote adds caution but also delays the full protective posture the team aims for. Even after the underlying software is widely installed, the security amendment won’t take effect until the separate voting criteria — again tied to validator support — are satisfied.

Market reaction: XRP price and trader behavior

Price action around $1.13–$1.14 resistance

Onchain and market data show buyers defended session lows after the upgrade news and pushed XRP back toward resistance in the $1.13–$1.14 range. Muted overall trading volume left traders waiting for confirmation above that zone before committing, a reaction consistent with upgrade uncertainty and wider market headwinds.

Macro and sector context influencing XRP moves

Major cryptocurrencies were trading in the red as renewed geopolitical tensions pushed oil higher, and institutional flows shifted across ETFs and custody products. Those macro currents can amplify traders’ conservatism around protocol upgrades, especially when activation thresholds remain unresolved.

Network health: validator migration, node diversity and vendor signals

Why node-count lag can persist despite validator leadership

Node operators run different hardware and operational policies; some prioritize continuity and keep v3.1.3 while monitoring the new client. Others, particularly validators maintained by exchanges or custodians, have faster deployment pipelines and sponsor early upgrades. That divergence explains why software leadership among validators exists even as overall node counts favor the older release.

Signals from ecosystem participants

Institutional and infra players are watching closely. Exchanges, custody providers, and broker-dealers often map their upgrade decisions to the trusted validator list and risk frameworks. The upgrade’s pace will reflect not just developer recommendations but also these institutional risk tolerances.

What to expect next and activation timeline

Steps toward hitting 80% endorsement

Expect an incremental climb: more validators are likely to upgrade as teams validate the client in staging and after positive initial runs. The security amendment vote could extend the timetable if validators choose to separate concerns and wait for audits or clarifications.

How users and integrators should prepare

Developers and enterprise integrators should test interoperability, back up nodes, and monitor validator signals closely. Wallet providers and exchanges should also coordinate communications to avoid confusion for end users about transaction behavior during the activation window.

Frequently Asked Questions

What exactly is required for the XRP Ledger upgrade to activate?

Activation requires 80% support from the trusted validator list. That means the validators that network participants trust must signal endorsement before the protocol change becomes active.

Why does validator leadership differ from node count?

Validator leadership refers to which validators (often those with more influence or reputation) run the new client. Node count measures total instances running a version. Operators upgrade at different speeds for operational and risk-management reasons, so these metrics can diverge.

Will the security amendment automatically follow the main upgrade?

No. The security amendment is a separate vote and is moving more slowly. It will only take effect after its own voting threshold is met, independent of the main software rollout.