1 hour ago
3
The XRP Ledger’s core server software has a new name and a hefty round of housekeeping. Version 3.2.0, released on June 15, marks the official rebrand from “rippled” to “xrpld,” a shift that’s been brewing under amendment XLS-0095 and signals a deliberate effort to put daylight between the open-source blockchain and Ripple, the company most people still confuse it with.
It’s a maintenance-heavy release, not a flashy feature drop. But for node operators and validators, the changes are significant enough to require immediate upgrades.
What actually changed
Configuration files, database paths, and metadata all change with the new branding. That means anyone running a node who doesn’t upgrade will find themselves dealing with compatibility headaches.
The meatier technical work comes via the “fixCleanup3_2_0” amendment. This single amendment retires over 30 older amendments in one sweep, eliminating legacy code that had accumulated across years of incremental updates.
Security fixes target several features that have been getting attention lately, including Single Asset Vaults, the Lending Protocol, and permissioned domains. The release doesn’t introduce these features. Rather, it patches bugs and hardens existing implementations that were activated in prior versions.
On the infrastructure side, developers get configurable NuDB block sizes, improved APIs, and optional TLS/mTLS for gRPC communication.
Performance gains and what the numbers suggest
Several reports suggest that v3.2.0 may reduce memory usage by approximately 30-40% compared to prior versions.
Version 3.2.0 follows v3.1.3, which was activated in late May 2026 and focused on fixes related to NFT functionality and the Lending Protocol.
The identity question and why it matters for investors
The rebrand from rippled to xrpld touches on one of the most persistent narratives in crypto: is XRP decentralized, or is it Ripple’s token? That question has dogged the asset through years of SEC litigation and market skepticism. By formally separating the server software’s identity from the Ripple brand, the XRPL community is building a paper trail of independence. Every configuration file, every GitHub commit, every documentation page now reinforces that this is community infrastructure, not corporate property.
Validators and node operators who delay upgrading face a more immediate concern. The changes to configuration paths and metadata mean that running outdated software isn’t just suboptimal, it’s potentially incompatible with the rest of the network.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
English (US) · 