XRP Ledger Operations announced on X on June 4 that XRP Ledger version 3.2.0 will be deployed to the mainnet, and the core server software will be renamed from “rippled” to “xrpld.” All infrastructure providers, validators, and node operators must complete system updates before migrating to the new XRPL mainnet; the development team confirmed that a detailed technical migration guide is being prepared.
3.2.0 Renaming Details and Mandatory Upgrade Requirements
The CLI (command-line interface) has been updated to reflect the new software name, showing “xrpld version 3.2.0” during version checks. In the announcement, XRP Ledger Operations said: “This transition will require some updates from infrastructure operators.” The development team confirmed that it is preparing a detailed technical operations manual to guide participants through the migration process, ensuring the continuity of consensus and network participation during the upgrade.
dUNL validator Vet publicly welcomed this announcement and said: “Market sentiment is temporary, but core protocol improvements are permanent.” Former Ripple CTO David Schwartz previously answered key questions about the 3.1.3 update, which ultimately passed with 100% unanimous approval.
RLUSD Wormhole NTT Integration: Confirmed Chains and Circulation Figures
According to official statements from Ripple and Wormhole dated June 4, 2026, RLUSD is now natively transferable between supported blockchain ecosystems via Wormhole’s NTT framework. Ripple confirmed target ecosystems including Optimism, Base, Ink, Unichain, and the XRPL EVM sidechain; RLUSD was previously natively issued on XRP Ledger and Ethereum. The Wormhole NTT framework supports rate limiting, access control, and supply accounting, allowing token issuers to maintain control and native functionality of the token during cross-chain transfers.
Wanchain has integrated RLUSD into its bridging architecture, supporting transfers between XRPL, Ethereum, Cardano, and Wanchain.
FAQ
What operational impact does renaming “rippled” to “xrpld” have on existing node operators?
Based on the official guidance from XRP Ledger Operations, all infrastructure providers, validators, and node operators must complete system updates before migrating to the new XRPL mainnet; the CLI has already been updated to reflect the new name. The development team confirmed that a detailed migration guide is being drafted, but as of the announcement date, the specific technical operations manual has not been officially released.
What confirmed feature differences are there between XRP Ledger 3.2.0 and 3.1.3?
The source text confirms that 3.1.3 (launched May 27, 2026) introduced multiple fixes for NFT, the custody (vault) system, permissioned domains, and components of lending protocols, and improved long-term network reliability by modifying fixCleanup3_1_3. The main confirmed changes in 3.2.0 are the renaming of the core software (rippled→xrpld) and broader modernization of the protocol-layer architecture; a complete list of specific new features has not been fully published as of the announcement date.
How does RLUSD integration via Wormhole NTT differ from earlier cross-chain solutions?
Wormhole’s NTT (native token transfer) framework allows RLUSD to retain the token’s native functionality during cross-chain transfers (including metadata, ownership, upgradability, and custom functionality). The issuer also maintains control over the token and it supports rate limiting and access control. This differs from traditional bridging architectures, which typically involve a “lock-and-mint” mechanism for assets and may introduce bridge contract risks.
