XRP Ledger Drops 3.2.0, Rebrands Core Server to "xrpld" — Rippled Off Into the Sunset 🌀

The XRP Ledger has released version 3.2.0 of its core server, formally rebranding the long-standing "rippled" software to "xrpld" as part of the XLS-0095 update. The change took effect on June 15 and is intended to reflect the network's independent ecosystem identity separate from Ripple.

The upgrade, which follows the v3.1.3 release in May, touches all configuration paths, server metadata, database directories and version naming. Existing validators and node operators are being asked to install updated configuration files and scripts to remain compatible with the new infrastructure.

A new amendment, "fixCleanup3_2_0," is being introduced to the mainnet alongside the release. It bundles security patches covering Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens and permissioned domains, while adding new invariant checks designed to prevent deleted accounts from leaving residual ledger artifacts.

The 3.2.0 update also ships several approved amendments to the mainnet and adds a suite of new developer tools to the XRP Ledger ecosystem. Developers behind the release have framed the cleanup work as part of an ongoing effort to strengthen consistency and reliability across the network.

Node operators and integrators have been directed to review the project's release notes for migration steps tied to the rebranding and the new amendment. $XRP remains the native asset of the ledger, and the changes are positioned as infrastructure-level maintenance rather than a protocol-level token event.