The XRP Ledger has launched version 3.2.0, introducing several infrastructure upgrades, developer enhancements, and network fixes. The release also replaces the long-standing “rippled” name with “xrpld” across the ecosystem. Meanwhile, validators and node operators must update their systems to remain compatible with the latest network changes.
Xrp Ledger Rebrands Core Infrastructure
The XRP Ledger introduced version 3.2.0 as part of its ongoing network development efforts. The update arrived weeks after the release of version 3.1.3. As a result, the network now includes several operational and infrastructure improvements.
A key change involves the rebranding of the core server software. The network officially replaced the “rippled” name with “xrpld” through the XLS-0095 update. Consequently, the software now reflects the broader and independent identity of the XRP Ledger ecosystem.
The change affects multiple system components across the network. Configuration paths, database directories, server metadata, and version labels now use the new naming structure. Therefore, validators and node operators may need to modify scripts and install updated configurations.
Upgrade Introduces Security Fixes and Developer Enhancements
The latest release also introduces the “fixCleanup3_2_0” amendment to the XRP Ledger. This amendment consolidates several approved security-related improvements. In addition, it strengthens multiple ecosystem features already operating on the network.
The update addresses components linked to Single Asset Vaults and the Lending Protocol. It also covers permissioned decentralized exchanges, Multi-Purpose Tokens, and permissioned domains. As a result, the network improves consistency across these expanding functionalities.
Developers also added new invariant checks within the release. These checks prevent deleted accounts from leaving behind ledger artifacts that could remain accessible later. Consequently, the ledger can maintain cleaner records and improve operational reliability.
The upgrade includes new tools designed for developers and infrastructure providers. Applications can now retrieve protocol information and server definitions without connecting to a live server. Therefore, developers can simplify integrations and reduce operational requirements.
This feature supports wallet providers, blockchain explorers, API services, and automation tools. Furthermore, it streamlines access to critical network information. The enhancement may reduce development complexity for services built on the XRP Ledger.
Infrastructure Performance Receives Major Improvements
Version 3.2.0 also delivers several performance-focused improvements. The release introduces configurable nuDB block sizes for database storage optimization. As a result, operators gain greater flexibility in managing storage resources.
The update adds optional TLS and mutual TLS support for gRPC servers. These additions strengthen communication security and improve enterprise-grade connectivity. Consequently, organizations operating XRPL infrastructure can implement stronger network protections.
Another notable change involves the network’s default peering port. The release shifts the default port from 51235 to 2459. Therefore, operators must review network configurations to ensure uninterrupted connectivity.
The upgrade also contains numerous fixes across several network functions. These fixes affect automated market makers, payments, Multi-Purpose Tokens, token escrows, order books, and RPC handling. As a result, the network improves efficiency and stability across multiple transaction types.
Developers temporarily disabled transaction invariants in version 3.2.0. The decision followed the discovery of a performance regression issue during deployment. However, the change does not alter current security protections because the invariants remain inactive in practice.
The XRP Ledger continues to expand its infrastructure while improving operational efficiency. Recent updates show increasing focus on scalability, developer accessibility, and enterprise readiness. Therefore, the latest release represents another step in the network’s broader technical evolution.
Validators and node operators are expected to adopt the new version promptly. The upgrade ensures compatibility with recently approved amendments and infrastructure improvements. As the ecosystem grows, regular software updates remain essential for maintaining network performance and functionality.
