XRPL 3.2.0 Is Live: rippled Becomes xrpld
XRPL LAB Daily Brief • June 17, 2026
Infrastructure Watch
XRP Ledger version 3.2.0 is now available, and the headline change for
operators is official: the reference server has moved from the historic
rippled name to xrpld.
This is not just a branding change. The migration can affect default
configurations, database directory paths, service checks, log monitoring,
dashboards, automation scripts, and runbooks that were built around the
old rippled name.
XRPL LAB's view: this is an operator-readiness release. The correct move is to verify the official migration instructions, back up configs, upgrade carefully, and confirm validator health from more than one signal.
What Changed
The server name transition is now real.
XRPL 3.2.0 renames the reference server implementation from
rippled to xrpld. Operators should expect
old assumptions to break if scripts, dashboards, or service checks are
hardcoded around the former name.
The release also introduces fixCleanup3_2_0, a cleanup
amendment bundle that includes fixes touching Single Asset Vaults, the
Lending Protocol, Permissioned DEX behavior, Multi-Purpose Token amount
validation, and permissioned domains.
Operator Checklist
Review these before and after migration.
- Back up the current XRPL server config before upgrading.
- Confirm the official migration path from
rippledtoxrpld. - Check database directory paths before restarting production services.
- Review systemd units, aliases, timers, and watchdog scripts.
- Update dashboards that search for the old process or binary name.
- Verify logs, peer count, validated ledger progress, quorum, and validator state.
- Confirm amendment status after the node is healthy.
Security Perspective
Upgrade windows are risk windows.
Operators should be extra careful during the migration window. Fake upgrade guides, spoofed release links, malicious copy-paste commands, and phishing messages often appear around major ecosystem changes.
The safest approach is simple: use official sources, inspect commands before running them, back up the config, verify checksums where possible, and confirm node health independently after the upgrade.
Why This Also Matters for AI Payments
XRPL infrastructure is becoming more automated.
Ripple's XRPL AI Starter Kit continues to push the network toward agentic payment use cases involving XRP and RLUSD. If software agents are going to pay for APIs, compute, data, and services, the underlying node infrastructure must be reliable, observable, and secure.
That makes the 3.2.0 migration more important. The future XRPL stack will not only serve human users. It may also support automated systems that expect fast settlement, predictable fees, and clear transaction finality.
Bottom Line
This is an infrastructure milestone.
XRPL 3.2.0 is the moment operators need to stop treating the
rippled to xrpld transition as upcoming and
start treating it as production work.
For XRPL LAB, the focus is clear: protect the validator, verify the node, update the monitoring layer, and keep the public dashboard honest.
Suggested Sources
Reference trail for today's brief.