XRP Ledger 3.2.0 Hits June 15: rippled Becomes xrpld

The XRP Ledger is about to change its core engine in a way it never has before. Version 3.2.0 is targeting June 15 for mainnet activation, bringing a long-awaited rename of the server software and a promise of up to 40% lower memory usage. Every validator has a deadline. Every XRP holder has questions. Here is everything you need to know.

What XRPL 3.2.0 Changes on June 15

On June 4, XRPL Operations posted on X: “XRP Ledger 3.2.0 is coming soon.” That single post sent developers, validators, and community members scrambling for details.

dUNL validator Vet confirmed the June 15 activation target in response to direct community questions. The date remains a target rather than a confirmed launch schedule from XRPL Operations itself.

As of June 8, the GitHub milestone was 98% complete, meaning the June 15 release date is not yet formally confirmed. The development team is clearly in the final stretch, but the timetable could still shift.

Version 3.2.0 is a pure infrastructure release. It does not introduce new protocol features but instead focuses on a historic rebrand, deep performance improvements, and long-term code stability.

Here is what this release brings to the network:

• Core server software renamed from rippled to xrpld
• Up to 30 to 40 percent reduction in server memory usage
• Bug fixes including rounding and number handling corrections
• Code cleanups and internal refactoring for long-term stability
• Expanded AI-powered testing and active bug bounty programs

This upgrade follows the successful activation of XRPL version 3.1.3, which went live in May 2026 and introduced fixes for NFTs, vault systems, permissioned domains, and lending protocol components.

Why rippled Is Getting a New Name

The rippled name has been linked to the XRP Ledger’s core server software since Ripple open-sourced it in 2013. For over a decade, it worked. Then the network grew up.

As the network transitioned to community-led governance and a distinct XRPL identity, the server retained its outdated name. Renaming it to xrpld aligns the software with the XRP Ledger and emphasizes its open, neutral nature.

Renaming the binary to xrpld cuts the implicit Ripple association, signals the network’s maturity as an independent open-source protocol, and gives every institution and developer building on the ledger a cleaner identity to build around.

Following the upgrade, node operators checking their software versions will see “xrpld 3.2.0” displayed in the command line for the first time. That small text change carries a message far bigger than it looks.

dUNL validator Vet wrote on X: “Market sentiment is temporary, but the core protocol improvements that our $XRP and other assets live on are permanent.” Ripple software engineer Mayukha Vadari echoed the sentiment, responding with the “100” emoji and saying “lots of good stuff.”

The 30 to 40 Percent Memory Drop and Why It Matters

Performance is the quiet engine of this release. Server memory usage is expected to fall by 30 to 40 percent, and that reduction carries real consequences for the whole network.

Internal structures within the XRPL can grow to consume over 20 gigabytes of RAM, which means nodes need a substantial amount of memory to participate. The development team’s goal is to lower the entry point for participation and support many more millions of transactions, accounts, and trust lines in the future.

A 30 to 40 percent cut in memory usage means cheaper node operations, lower hardware barriers for new validators, and a broader, more accessible path to network participation. That is a direct win for decentralization.

The upgrade will support the network’s growth in transaction volume, tokenization, and DeFi activities, while also supporting long-term stability and scalability without introducing new user-facing features.

Reports have linked version 3.2.0 to memory savings of up to 40 percent. However, XRPL Operations has not yet released the final technical notes or public benchmarks supporting that exact figure. The full numbers will land with the official release documentation.

What Validators and Node Operators Must Do Before June 15

This upgrade is not optional for anyone running the network. Validators and node operators must act before the activation date or risk losing their place in network consensus.

Nodes still running the old rippled binary after the June 15 activation will fall out of consensus and become effectively isolated from the network, unable to serve current ledger data.

Nodes running the old rippled binary post-activation will fall out of consensus and become effectively isolated from the network. This can lead to operational risks for exchanges and services, including stale data and failed transactions.

This is also not a simple one-file binary swap. The migration touches multiple layers of infrastructure:

• Systemd service files referencing the old “rippled” binary name
• Deployment scripts and automation workflows
• Monitoring dashboards and command-line health checks
• Docker images and CI/CD pipelines
• Internal documentation and support tooling using the old name

Node operators may need to revise service files, scripts, monitoring tools, and command-line checks. XRPL Operations confirmed it is preparing a detailed playbook. That guide had not been released as of June 8, so operators should watch XRPL Operations channels closely.

Network data indicates that about 84% of XRPL nodes have already adopted version 3.1.3. This level of adoption suggests the ecosystem is preparing for a relatively smooth migration to the new software version. Operators should test the upgrade on testnet or devnet before applying it to mainnet.

What XRP Holders Need to Know Right Now

If you hold XRP in a wallet or on an exchange, you do not need to take any action.

Your wallet address, XRP balance, private keys, and transaction history are completely untouched by this upgrade. It operates entirely at the server infrastructure layer with zero impact on regular holders.

XRP traded near $1.17 on June 9, up roughly 2.5% over seven days amid broader market selling. The token remains roughly 70% below its July 2025 high near $3.65, a gap that has kept many retail investors cautious about short-term prospects.

Over 25 million XRP were withdrawn from exchanges during this period, often interpreted as a sign that holders are putting their assets to long-term storage rather than selling them. At the same time, the number of wallets holding at least 10,000 XRP hit a record 332,230 addresses, the highest number ever recorded.

A server release does not guarantee higher demand for XRP on its own. But the long-term benefit is indirect: a more efficient, lower-cost network infrastructure supports the XRPL DeFi ecosystem, faster transaction settlement, and the kind of institutional-grade reliability that underpins broader XRP adoption. The benefit to holders is quiet today and compounding over time.

The XRP Ledger 3.2.0 upgrade may not flash across the price ticker, but for anyone who has watched this network battle through legal uncertainty and quietly build its way forward, this release is a milestone. The name “rippled” served its era. “xrpld” is the server’s name from here forward, and the 40% memory reduction underneath it may be the most important long-term gift the development team has handed the ecosystem. If you run a validator, the clock is moving. If you hold XRP, the network you believe in just got a little stronger. Drop your thoughts in the comments below and share the conversation with the community on X using #XRPL.