XRP Ledger v3.2.0 Renames Its Core Server From rippled to xrpld

The XRP Ledger's version 3.2.0 went live on 15 June, and its most visible change was a name. The reference server software that XRPL node operators run, called rippled since the network's early days, is now xrpld. XRPL Operations, the group that maintains the software, said the rebrand "reflects the broader, increasingly Ripple-independent XRPL ecosystem and reduces confusion with Ripple's commercial offerings," in a statement Coinspeaker carried. The rest of the release was maintenance work on the server's internals. It brought no new user-facing features and no amendments, the on-ledger votes through which XRPL validators switch protocol changes on.

What a reference client's name signals

A reference client is the primary implementation of a network's protocol, the program validators and other node operators run to follow consensus, validate transactions and serve data to wallets and exchanges. Its name is one of the first things an outside observer reads, and on the XRP Ledger that name pointed at a company. Ripple built the ledger and sells commercial payment products that settle on it, and the shorthand of running rippled made the open network and the vendor hard to separate at a glance. The stated reason for the change addresses that directly: XRPL Operations described an ecosystem that has grown broader and less dependent on Ripple, and a name that no longer described it. Renaming a binary does not redistribute validator control or change who writes the code. Amendments pass the same way. What changes is the label attached to all of it, and the label is the version of the network most outsiders ever see.

Refactoring, rounding and hardening

Version 3.2.0 is a maintenance release, and XRPL Operations presented it as one. The work covered internal server refactoring, corrections to numerical handling and rounding, and security hardening that included AI-assisted testing and an expanded bug bounty, the same Coinspeaker report said. What is absent matters as much: with no new user-facing features, wallets, exchanges and payment integrators had nothing new to support, and with no amendments, validators had nothing new to vote on. That makes 3.2.0 a low-stakes upgrade in principle, one that changes how the server behaves internally without changing what the ledger does.

Core server renamed from rippled to xrpld.
Server refactoring and internal cleanup.
Fixes to numerical handling and rounding.
Security hardening, including AI-assisted testing and an expanded bug bounty.
No new user-facing features and no amendments.

A memory number without a benchmark

A figure of 30% to 40% lower memory use circulated alongside the release. It stands unverified. A single outlet sourced it to developer commentary rather than a published benchmark, and no measurements accompanied the release to support it. Memory footprint is not a trivial detail for XRPL operators, because it sets the hardware floor for running a validator or a server that keeps ledger history, and a reduction of that size would lower the cost of participating. Without a benchmark that specifies hardware, history depth and workload, there is nothing to check the number against.

84% of nodes were still on v3.1.3

The practical question is how fast the network moves. As of 8 June, a week before 3.2.0 shipped, 84% of XRPL nodes were still running v3.1.3, a count Coinspeaker cited. Node upgrades follow operator schedules, not release dates, and a maintenance release with no amendments carries little urgency, since nothing on the ledger stops working for an operator who stays put. That also makes the rename a slow signal instead of an event. The name xrpld becomes the name of the network's software only once operators actually run it, and the pace of that rollout, not the release notes, will show whether the shift away from the Ripple label is a description or an intention.