The XRP Ledger Foundation released version 3.2.0 of the network's core server software, renaming the server binary from 'rippled' to 'xrpld' under the XLS-0095 standard. The renaming reflects the XRP Ledger ecosystem's ongoing shift toward independent identity separate from Ripple the company, as the network now operates with its own foundation, standards process, developers, validators, and infrastructure teams. The release also introduces an updated GPG signing key for automatic upgrades, retires legacy amendments, and addresses bugs in Single Asset Vault functionality.
XRP Ledger Foundation Renames Core Server Binary Under XLS-0095
The XRP Ledger's core server binary has been renamed from 'rippled' to 'xrpld' in version 3.2.0 under the XLS-0095 standard. The naming change addresses longstanding confusion between Ripple the company, XRP the native asset, and the XRP Ledger blockchain network. Ripple is a company, XRP is the native asset, and the XRP Ledger is the blockchain network. The new 'xrpld' name reflects the network's infrastructure rather than pointing to Ripple the company. The XRP Ledger now operates with its own foundation, standards process, developers, validators, and infrastructure teams.
Node Operators Face GPG Signing Key Updates and Compatibility Requirements
Node operators must manage the v3.2.0 upgrade to maintain compatibility with the XRP Ledger network. The release includes an updated GPG signing key for automatic upgrades, affecting how operators verify authentic software releases. Operators who fail to maintain required versions and amendment support can experience local synchronization issues or become amendment blocked. The updated GPG signing key addresses security requirements for software distribution on networks that support value transfer. Individual infrastructure providers, exchanges, validators, and services running XRPL nodes need to implement the upgrade to avoid compatibility problems.
XRP Ledger Foundation Retires Legacy Amendments in Version 3.2.0
The v3.2.0 release retires legacy amendments as part of ongoing protocol maintenance. The retirement removes old features, older code paths, outdated assumptions, and unused amendments that accumulate over time in blockchain networks. Removing legacy components reduces maintenance burden and allows developers to focus on current protocol priorities. The cleanup work supports protocol stability by addressing technical debt before it creates operational problems.
Single Asset Vault Bug Fixes Support DeFi Functionality Expansion
The v3.2.0 release fixes bugs in Single Asset Vault functionality. Single Asset Vaults are part of the XRP Ledger's expansion into advanced on-chain financial functionality beyond its historical focus on payments, transfers, and exchange-style functions. The ecosystem has been developing more complex primitives, including lending-related standards and vault mechanics. Bug fixes in vault functionality address engineering requirements for DeFi-style functions, where mistakes can affect user funds, liquidity, and application reliability.
FAQ
What did the XRP Ledger Foundation change in version 3.2.0?
The XRP Ledger Foundation released version 3.2.0, which renames the core server binary from 'rippled' to 'xrpld' under the XLS-0095 standard. The release also includes an updated GPG signing key for automatic upgrades, retires legacy amendments, and fixes bugs in Single Asset Vault functionality.
Why did the XRP Ledger Foundation rename the server binary?
The renaming from 'rippled' to 'xrpld' reflects the XRP Ledger ecosystem's shift toward independent identity separate from Ripple the company. The XRP Ledger now operates with its own foundation, standards process, developers, validators, and infrastructure teams. The new name points to the network itself rather than Ripple the company.
How does the v3.2.0 upgrade affect node operators?
Node operators must manage the v3.2.0 upgrade to maintain compatibility with the XRP Ledger network. The release includes an updated GPG signing key for automatic upgrades. Operators who fail to maintain required versions and amendment support can experience local synchronization issues or become amendment blocked.
