XRP Ledger v3.2.0 is a maintenance release for the network's core server software, focused on cleaning up code, reducing memory usage, and patching newer DeFi features rather than shipping an
XRP Ledger v3.2.0 is a maintenance release for the network's core server software, focused on cleaning up code, reducing memory usage, and patching newer DeFi features rather than shipping anything flashy for everyday users. It went live on June 15, and the headline change is a name: the reference server that has been called Rippled since 2013 is now XRPLD. The interesting part sits underneath that rebrand, where a batch of security fixes is quietly hardening the rails that XRPL's fast-growing stablecoin and lending activity now runs on.
The rename is the most visible part. Under the XLS-0095 spec, the core server binary moved from Rippled to XRPLD, and the default config file switched from rippled.cfg to xrpld.cfg. That affects configuration paths, database directories, and server metadata, so validators and node operators must update their deployment scripts before migrating. The change is cosmetic for token holders but symbolic for the network: it strips Ripple's name off community-maintained software and reinforces the separation between the company and the open-source ledger.
Beyond the name, v3.2.0 retires a stack of amendments that have been active for more than two years and continues breaking the codebase into smaller modules. The release also projects a 30% to 40% reduction in memory usage, though that figure comes from developer commentary and secondary coverage rather than published benchmarks. There is a new configurable block-size option for storage, and the default peering port has moved from 51235 to 2459.
The upgrade also ships a new amendment, fixCleanup3_2_0, and this is where its most consequential work sits. It bundles targeted bug fixes and new checks across the ledger's newer building blocks:
None of these are features. They are the plumbing that keeps on-chain lending, vaults, and tokenized assets behaving correctly under real money. The Lending Protocol also passed an independent security audit ahead of the release, and @Ripple has publicly backed the amendment, which adds confidence around the changes. The work builds directly on v3.1.3, the May cleanup that handled expired NFT offers, vault bugs, and lending accounting.
Directly, not much. If you hold or send XRP, v3.2.0 does not add anything you will notice. Its value is indirect. The vaults, lending markets, and MPTs that these fixes shore up are the same primitives that wallets and apps are starting to expose to ordinary users. As those integrations arrive, the payoff is more reliable lending markets and tokenized-asset products sitting on code that has been audited and patched, not on rough edges.
Developer-facing changes help here too. A new flag lets apps pull XRPL protocol and server definitions without a live server connection, which makes it easier to build wallets, explorers, and APIs. XRPL also gained support for the x402 payment standard, letting AI agents pay for services using $XRP or $RLUSD.
The timing matters because v3.2.0 lands as XRPL's dollar layer expands rapidly. Stablecoin supply on the ledger has climbed past $908 million, up more than 20% over the past month, and is closing in on the $1 billion mark that analysts have flagged as the next real test of the trend.
Ripple's RLUSD is doing nearly all of the work, accounting for roughly 94% of the ledger's stablecoins. XRPL now hosts about 51.7% of RLUSD's total circulation, more than sits on Ethereum, according to data from treasury firm Evernorth.
Adoption is climbing but not finished. XRPL Operations (@XRPLOperations) put network adoption at 42% this week, and XRPL Explorer data shows 84 trusted validators, or 55.63% of the set, running xrpld v3.2.0. But running the new server is not the same as approving the amendment it carries: validators cast a separate vote on fixCleanup3_2_0, and support there sits near 40%, short of the 80% supermajority it must hold for two straight weeks to activate. That some validators have upgraded without yet voting the amendment through reflects a deliberate, safety-first pace rather than a stalled rollout.
That split is the current tension. The server software is live and spreading, but the amendment bundled with it isn't active yet, and node operators who delay upgrading risk running incompatible software once the vote clears.
Sources:
