Overview
- Version 3.2.0 went live on Monday, June 15 and formally changes the core server binary name from rippled to xrpld.
- The rebrand alters default filenames, server metadata and database directories and also changes the default peering port from 51235 to 2459, forcing operators to update configuration files and automation scripts.
- The release activates the fixCleanup3_2_0 amendment that retires more than 30 legacy amendments and applies security and validation fixes for Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens and permissioned domains.
- New developer and infrastructure features include tools to fetch protocol info without a live server, configurable NuDB block sizes and optional TLS/mTLS for gRPC, and early reports suggest a roughly 30–40% reduction in memory use though formal benchmarks are still pending.
- Operators are being urged to upgrade to avoid compatibility or consensus problems, community maintainers have yet to publish a comprehensive migration playbook, and high-profile operators such as David Schwartz have already moved hubs to xrpld as the ecosystem adds x402 support and sees strong RWA inflows.