- XRP Ledger renames core server from rippled to xrpld, requiring immediate node migration.
- fixCleanup3_2_0 amendment bundles bug fixes for vaults, lending protocol, and MPT amounts.
- The update removes 30+ legacy amendments, reducing code complexity and maintenance requirements.
The XRP Ledger has released version 3.2.0 of its core server software, marking one of the most important maintenance milestones in recent years. The headline change is a full rename of the reference server implementation from rippled to xrpld, a move designed to further distinguish the open-source blockchain infrastructure from Ripple, the company.
Node operators and validators are being advised to upgrade immediately to ensure service continuity. The rename affects default configuration paths, database directory paths, and RPC metadata, including the server’s user agent string, requiring additional migration steps beyond a standard update.
What Changed
The update introduces the fixCleanup3_2_0 amendment, which bundles several targeted bug fixes across key protocol areas:
- Precision and rounding fixes for Single Asset Vaults and the Lending Protocol
- Corrections to the ValidPermissionedDEX invariant
- Validation of non-canonical Multi-Purpose Token amounts
- A zero DomainID check for permissioned domains
- A new invariant ensuring deleted accounts leave no accessible artifacts behind
More than 30 legacy amendments that have been active for over two years are being retired through this release, cleaning out code that accumulated across multiple development cycles and reducing the maintenance burden on the codebase going forward.
Optional TLS and mutual TLS support has been added for gRPC servers, strengthening connectivity security for enterprise deployments that require encrypted communications between nodes and applications.
The default peering port has changed from 51235 to 2459, and the release includes dozens of targeted fixes across automated market makers, payment processing, multi-purpose tokens, token escrows, order book management, and RPC handling.
What the Community Said
Reactions from developers and XRP community members were mixed. Some welcomed the cleanup as a step toward better long-term stability. Others questioned whether removing legacy code without introducing significant new features represented cautious development rather than forward momentum.
Supporters pushed back on that framing directly, describing the update as incorporating crucial security and infrastructure improvements rather than playing it safe.
XRPL validators and node operators are encouraged to upgrade as soon as possible to maintain network compatibility and benefit from the security and infrastructure improvements included in this release.
Related: XRPL Foundation Teases XRP Ledger Native Privacy Amid Zcash Crisis
Disclaimer: The information presented in this article is for informational and educational purposes only. The article does not constitute financial advice or advice of any kind. Coin Edition is not responsible for any losses incurred as a result of the utilization of content, products, or services mentioned. Readers are advised to exercise caution before taking any action related to the company.
