XRP Ledger shipped its latest software upgrade, but adoption tells a fragmented story. The new version leads in validator count, yet by the raw number of nodes running the network, the older v3.1.3 still dominates. That split matters because the ledger's consensus model requires broad agreement to finalize changes.
The upgrade bundles a security amendment, but that fix operates on a separate voting track from the core software. Validators must cast an independent vote to activate the amendment, and it needs 80% approval from the network's trusted validator list to take effect. Neither has crossed that threshold yet, according to CoinDesk.
This two-track rollout reflects a deliberate caution in the XRPL ecosystem. A validator running new software doesn't automatically enforce a new rule; the security amendment sits dormant until the voting supermajority signs off. That gap between software availability and rule activation can last weeks or longer, depending on how quickly operators test and endorse the change.
Validator fragmentation across software versions isn't unusual during upgrades, especially on older chains with decentralized operator bases. But it does create a window where the network runs multiple codebases in parallel. If validators running different versions disagree on a core rule, consensus can break. The 80% threshold acts as a safety valve, ensuring that no major rule change sneaks through without overwhelming agreement.
The real test comes next. If the security amendment clears the 80% vote, lagging node operators will face pressure to update. If adoption stays slow, the network must decide whether to fork or wait. CoinDesk did not specify a timeline for either outcome or whether the amendment addresses a known vulnerability. The newsroom will track the vote as it progresses.