XRP Ledger has enforced a major protocol clean-up by activating its fixCleanup3_2_0 amendment, immediately blocking any mainnet node running software older than version 3.2.0 from participating under the updated rules.
The change, which took effect after a two-week on-ledger governance process, means infrastructure operators still on version 3.1.0 or below are now “amendment blocked” and can no longer follow validated ledgers on the main network until they upgrade.
Data from XRPScan shows the fixCleanup3_2_0 amendment went live after it was backed by 30 of the 35 trusted validators that voted, with five validators opposing the change. That level of support gave the proposal 85.71% backing, comfortably above the 80% threshold required for two consecutive weeks before any amendment can be activated on XRP Ledger.
The decision primarily affects organisations that run their own XRPL infrastructure – including exchanges, wallet providers, payment companies and developers – rather than ordinary holders of XRP. Users who keep XRP in self-custody wallets do not need to swap their tokens, move funds or take any other direct action as a result of the upgrade.
Technical clean-up, not a new product
The fixCleanup3_2_0 amendment packages a series of protocol corrections that shipped with the XRP Ledger 3.2.0 release. It does not introduce any new user-facing features and does not change the supply of XRP.
Among the adjustments are precision and rounding fixes for Single Asset Vaults and the Lending Protocol, aimed at ensuring more accurate handling of balances and calculations. The update also fixes an invariant associated with valid offer deletions on the Permissioned DEX, addressing a corner case in how those offers are removed from the ledger.
Further changes allow non-canonical Multi-Purpose Token amounts to be validated, add a zero DomainID check for permissioned domains, and implement a new invariant to ensure that deleted accounts do not leave behind directly accessible objects on the ledger.
Developers have characterised version 3.2.0 as a clean-up and maintenance release. As well as bundling the latest protocol corrections, it retires amendments that had been active for more than two years and continues an internal reorganisation that splits the libxrpl codebase into smaller, more manageable modules to simplify future maintenance.
Majority of validators already on 3.2.0
Figures from XRPLdata after activation underline that much of the network had already moved to the new release.
A total of 105 validators – around 70% of the validator set – were running version 3.2.0, while 35 validators, or 23.33%, remained on version 3.1.3. Other node operators showed a similar pattern: 582 nodes, representing 68.88% of that group, had upgraded to 3.2.0, with 228 nodes, or 26.98%, still using version 3.1.3.
Although version 3.1.3 sits above the range highlighted in XRPScan’s amendment-block warning, XRPL developers have urged every operator to complete the move to 3.2.0 to avoid compatibility issues and ensure full alignment with the new protocol invariants.
‘rippled’ renamed ‘xrpld’ in June release
Version 3.2.0, released in mid-June, also includes a significant rebranding of XRPL’s reference server implementation, which has been renamed from “rippled” to “xrpld”. The change flows from XLS-0095, a proposal intended to tie the software’s identity more directly to XRP Ledger itself.
That rename affects more than just the server binary. Operators upgrading from version 3.1.3 are required to rename their configuration file from rippled.cfg to xrpld.cfg and adjust all associated paths and tooling, including database directories, packages, scripts, deployment configurations, service definitions and related metadata.
XRPL’s migration documentation sets out the steps needed to preserve existing node data while switching to the new naming scheme and code layout, aiming to minimise disruption for operators during the transition.
Upgrade comes amid growth in tokenised real-world assets
The network-wide clean-up follows a period of rapid expansion in tokenised real-world assets (RWA) on XRP Ledger.
According to figures reported on 26 July by crypto.news, XRPL added around $2.6bn in RWA value over six months, excluding stablecoins. That placed it second for net RWA inflows over the period, behind BNB Chain’s roughly $3bn, with Stellar next on about $2.1bn.
Across the ledger, the combined value of distributed and represented RWAs reached approximately $4.38bn, with stablecoins contributing a further $995.12m. Together, those totals pushed the overall figure above $5.37bn.
For US-based firms using XRPL to power tokenised-asset platforms, payment rails or exchange infrastructure, the fixCleanup3_2_0 activation functions as an operational mandate rather than a regulatory change. Businesses must keep server software compatible with the now-enforced minimum of version 3.2.0 if they are to avoid service outages as activity on the ledger continues to grow.
