XRP Ledger Enforces Mandatory Node Upgrade to Version 3.2.0

The amendment successfully cleared the required 80% consensus threshold after securing 30 votes from the 35 participating trusted validators. Nodes still running legacy software are now classified as amendment-blocked, meaning they are unable to process or follow the latest validated ledger rules. While this change targets exchanges, wallet providers, and payment services, individuals holding XRP in self-custody wallets remain unaffected and require no action.

Beyond basic compatibility, version 3.2.0 introduces critical technical maintenance, including precision fixes for Single Asset Vaults, the Lending Protocol, and the Permissioned DEX. The update also formally rebrands the core server software from rippled to xrpld. This transition requires operators to manually rename configuration files, such as rippled.cfg to xrpld.cfg, and update database paths and service definitions to ensure operational continuity. Developers emphasize that these changes are strictly architectural, intended to streamline the codebase and retire long-standing amendments as the network continues to scale its real-world asset tokenization efforts.