XRP Ledger v3.2.0 Upgrade Nears Full Activation as Validator Adoption Hits 55%

The XRP Ledger (XRPL) is moving closer to a full xrpld v3.2.0 upgrade, with validator adoption now exceeding 55%. According to XRPL Explorer data, 55.63% of the validator set (84 validators) are running v3.2.0, while 353 network nodes (42.12%) have upgraded to the latest software. In comparison, version 3.1.3 remains active on 58 validators (38.41%) and 440 nodes (52.51%).

On the XRP Ledger, trusted validators approve protocol changes, and a network upgrade requires approval from over 80% of trusted validators for two consecutive weeks. Currently, only 25% more validators need to migrate to the new server for the v3.2.0 implementation to succeed.

Version 3.2.0 includes infrastructure improvements, bug fixes, and developer enhancements. A notable change is the official renaming of the main server software from rippled to xrpld, under the XLS-0095 proposal. This change, effective June 15, affects configuration paths, server metadata, database directories, and version naming, requiring validators and node operators to update their configurations and deployment scripts.

The release also introduces the fixCleanup3_2_0 amendment, which contains multiple security fixes for Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges (DEXs), Multi-Purpose Tokens (MPTs), and permissioned domains. It adds new invariant checks to prevent deleted accounts from leaving ledger artifacts, enhancing ledger consistency and reliability. Additionally, it allows users to obtain XRP Ledger protocol information and server definitions without running a server, streamlining integration for wallets, APIs, blockchain explorers, and automated tools.

Support for the fixCleanup3_2_0 amendment currently stands at 40%, far short of the threshold needed for activation. However, Ripple’s backing has instilled optimism. The XRP Ledger lending protocol also passed a critical audit, boosting confidence in the upgrade.

Despite progress, a GitHub report (#7581) highlights potential validator migration issues. The report notes that “the service log shows the correct new validator pubkey, however the actual server is running with the old pubkey stored in wallet.db.” This discrepancy could complicate the migration process.

Source: https://coingape.com/xrp-ledger-v3-2-0-full-upgrade-inches-closer-as-validator-adoption-hits-55/