XRPL 3.2.0 Renames rippled to xrpld in Cleanup Release

Steady attention without excessive speculation.

The release does three main things. First, it adopts the xrpld name under XLS-0095. Second, it retires amendments that have run for over two years. Third, it ships a new bug-fix amendment called fixCleanup3_2_0.

What Shipped in XRPL 3.2.0

The XRPL 3.2.0 Renames update is primarily a maintenance and cleanup release. While XRPL 3.2.0 Renames the reference server from rippled to xrpld, it does not introduce major retail-facing features. Instead, the release reduces technical debt, continues the modularization of the libxrpl library, and streamlines the codebase ahead of future XRP Ledger upgrades.

The official blog frames it plainly. It says the release “retires amendments that have been activated for over two years, continues the modularization of libxrpl, and renames rippled to xrpld.” You can read the full notes on the xrpl.org blog.

The release also adds smaller upgrades. For example, operators can now set a configurable nudp_block_size between 4K and 32K. Logs now show peer public keys while masking IP addresses. The ledger_entry API also gains new options.

Why rippled Became xrpld

The rename follows XLS-0095, a community standard first proposed in October 2025. XRPL 3.2.0 Renames the reference server from rippled to xrpld, reflecting how far the network has moved from its Ripple company roots.

The daemon first shipped as rippled before 2013. Since then, the XRP Ledger Foundation and outside developers have driven the project forward. According to XLS-0095, “over 1000 nodes run the application,” with contributions from developers around the world.

So the change runs deeper than branding. The binary becomes xrpld, and the config file becomes xrpld.cfg. The C++ namespace also shifts from ripple to xrpl. On top of that, package names and Docker images change.

How 3.2.0 Builds on Prior Releases

XRPL 3.2.0 Renames rippled to xrpld as part of a broader cleanup effort that has been unfolding across recent releases. The prior release, 3.1.3, shipped in May 2026 with its own bundle, fixCleanup3_1_3. That amendment activated on May 27, 2026, according to XRPScan. The latest XRPL 3.2.0 Renames update continues that maintenance-focused approach while reducing technical debt and simplifying the codebase.

Earlier releases focused on features instead. For instance, they added the Permissioned DEX, the Lending Protocol, and Multi-Purpose Tokens. Now the maintainers are circling back to harden those systems and prune old code. In short, 3.2.0 trades new features for a cleaner, leaner foundation.

Retired Amendments, Explained

Amendments are how the XRPL upgrades its protocol. Validators vote on each one. Once 80% agree for two weeks, a two-week timer activates the change.

After about two years live, an amendment can be retired. The old conditional code then leaves the source entirely. As a result, the feature becomes permanent core protocol rather than an optional flag.

Version 3.2.0 retires a long list. For instance, it includes Checks, NonFungibleTokensV1, DepositAuth, NegativeUNL, TicketBatch, and many fix amendments. Behavior stays the same for users, yet the codebase grows lighter and easier to maintain.

What fixCleanup3_2_0 Fixes

The release adds one new amendment, fixCleanup3_2_0, through PR #7037. It bundles several bug fixes for the network’s newer DeFi features.

Specifically, the fixes target precision and rounding in Single Asset Vaults and the Lending Protocol. They also correct permissioned DEX behavior and add stricter validation for Multi-Purpose Tokens. In addition, a zero DomainID check now guards permissioned domains.

On top of that, the amendment adds a new invariant called AccountRootsDeletedClean. It also fixes an invariant that fired wrongly on valid offer deletions. Explorers do not yet list the amendment ID, so activation should follow soon through validator voting. You can track its status on XRPScan.

What XRPL 3.2.0 Means for Node Operators

For node operators, the rename brings real work. Default config files, database paths, and package names all change. So scripts, monitoring, and automation will need updates.

To ease the move, the maintainers ship a temporary bridge. A rippled-to-xrpld symlink and a config fallback come with the release. However, both disappear after six months.

Operators can follow the official migration guide for the exact steps. For now, the GitHub repo stays at XRPLF/rippled, with forwarding planned as a later step.

Market Reaction and What Comes Next

The market response stayed muted. XRP traded near $1.15 to $1.24 through mid-June 2026. Some reports noted a brief move toward $1.17, yet no clear shift tied to the release alone.

That pattern is normal. Infrastructure upgrades rarely move price the way feature launches or regulation do.

Looking ahead, three things matter most. First, the activation of fixCleanup3_2_0 through validator voting. Second, how fast operators upgrade before the six-month window closes. Third, whether that deprecation window strains exchange and tooling support.

So far, community sentiment reads positive, and most builders frame XRPL 3.2.0 as an infrastructure win. This article is for information only and is not financial advice.