XRP Ledger v3.2.0 targets June 15, renames rippled to xrpld

XRPL targets June 15 for v3.2.0 mainnet. The release renames “rippled” to “xrpld” and aims to cut memory use by 30–40%.

XRPL Operations called the rollout “coming soon” on June 4, so June 15 is a target, not a lock. See the official post: XRPL Operations on June 4.

What changes
- The core daemon is renamed to xrpld. Operators will see “xrpld version 3.2.0” after upgrade. XRPL Operations on June 4
- Developers expect 30–40% lower memory use. This figure comes from developer commentary; no official performance docs were published as of June 8.
- No user-facing features. The scope is refactors, performance, numerical handling, and security hardening.

What operators must do
- Validators and nodes must upgrade before migration. Non-upgraded servers can fall out of consensus and fail to serve current ledger data. XRPL Operations on June 4
- Scripts and services referencing “rippled” will break post-migration. Update units, monitors, and package sources to “xrpld.”
- XRPL Operations promised a migration playbook ahead of deployment. XRPL Operations on June 4

Market check
- XRP traded at $1.13–$1.15 into the upgrade window, briefly spiking ~7% to $1.17 before retracing.
- The token remains ~70% below the July 2025 peak near $3.65. The announcement drew a muted price reaction.