XRP Ledger version 3.3.0 was released last week, drawing attention to the network’s progress in upgrading to the latest version. RippleX software engineer Mayukha Vadari has weighed in on the importance of an upgrade progress metric, clarifying how adoption rates are measured.
ETH
SOL
BSC
ROBINHOOD
USDT
AAPLDiscussion over update thresholds
The debate began after an X user highlighted that XRP Ledger’s unique node list (UNL) validators had met the “Sufficiently Updated” threshold of 80% for version 3.3.0 of the xrpld server. This prompted hopes in the community that amendment voting could accelerate now that the minimum has been reached among validators.
Community member Offledger subsequently questioned whether the “Sufficiently Updated” metric should factor in the entire network or only validators. Another participant suggested using exact numbers of non-validating nodes rather than percentages, since software versions often differ widely among these nodes. He referenced XRPScan data showing 74 nodes using version 3.3.0 and 58 still on version 3.2.1.
Offledger explained that the upgrade consideration always refers to the entire XRP Ledger network, not only UNL validators. He estimated that about 32% of the network had transitioned to version 3.3.0, while 68% still operated on 3.2.1. Offledger noted, “A wee way to go yet,” emphasizing that widespread adoption is still pending.
| xrpld Version | Number of Nodes |
|---|---|
| 3.3.0 | 74 |
| 3.2.1 | 58 |
Clarification from RippleX engineer
Mayukha Vadari clarified that most validators rely on the 80% “Sufficiently Updated” threshold as a reference. She noted that achieving 80% among the UNL acts as the minimal requirement for upgrade-related voting, rather than reflecting full network adoption. This highlights the ongoing challenge of achieving network-wide consensus during major software rollouts.
Vadari explained that the 80% updated rate is the minimum for validator-driven amendments, but broader upgrades require a larger share of the entire network.
Understanding the XRP Ledger’s network structure
The conversation has drawn attention to the difference between UNL validators and the broader distribution of software versions across the XRP Ledger. The xrpld server is one of two main software types that support the XRP Ledger and operates in several specialized modes.
In its main peer-to-peer (P2P) mode, xrpld serves as the backbone of the network, including validator nodes. Validators play a central role by securing the XRP Ledger through consensus. Each server, using its unique node list (UNL), identifies trusted validators to participate in consensus and help prevent collusion.
Mini dictionary: Unique Node List (UNL) is a list of validators that a node trusts for consensus. Each XRPL server configures its own UNL, and consensus is reached only among mutually trusted nodes, making the network resilient to certain types of attacks.
Aside from validators, hub servers relay messages across the network, and API servers enable applications to access blockchain data, submit transactions, and monitor ledger activity. All together, these servers form a decentralized peer-to-peer network to process transactions and maintain the shared state of the XRP Ledger.
The distinction between validator nodes and the broader network is critical in assessing upgrade progress, as adopting the latest software version across both segments is key to overall network performance and security.
