The XRP Ledger's core server software has been updated to version 3.2.0, and the binary is no longer called 'rippled'. It's now 'xrpld' under the XLS-0095 specification, a change that signals a deliberate separation from Ripple the company.
Why the rename matters
The shift from rippled to xrpld is more than a rebrand. It reflects a broader move toward an XRPL-native identity, distancing the network's infrastructure from the corporate entity that originally created it. The update also includes an updated GPG signing key for automatic upgrades, giving node operators a way to verify the authenticity of the new binary.
Technical changes in the release
Version 3.2.0 retires legacy amendments as part of the upgrade. It also fixes bugs in Single Asset Vaults, a feature that lets users lock up XRP for lending or other on-chain purposes. Those fixes address issues that could have affected vault functionality. The XRP Ledger ecosystem is expanding beyond simple payments into lending, vaults, and other on-chain features, making this release part of a larger push to support more financial primitives.
Risks for node operators
Node operators must manage the upgrade carefully. The release notes warn that failing to update properly could lead to synchronization issues or becoming amendment blocked — a state where a node falls out of sync with the network because it doesn't support a newly activated amendment. With the ecosystem adding new features, staying current is more important than ever.
The new binary is available now. Node operators should plan their upgrade window to avoid disruption.
