The $XRP Ledger community is racing to resolve a series of technical issues in xrpld v3.2.0 before the scheduled activation of the fixCleanup3_2_0 amendment on July 29. What the Amendment Doe
The $XRP Ledger community is racing to resolve a series of technical issues in xrpld v3.2.0 before the scheduled activation of the fixCleanup3_2_0 amendment on July 29.
Version 3.2.0 retires several long-active amendments, introduces a new cleanup amendment and bug fixes, and renames the rippled binary to xrpld. The fixCleanup3_2_0 amendment bundles bug fixes affecting Single Asset Vaults, the Lending Protocol, the permissioned DEX, Multi-Purpose Tokens, and permissioned domains.
The amendment currently holds 85.71% validator support and is scheduled to activate on July 29, 2026, at 09:57 UTC. Support must remain at or above 80% throughout the countdown, otherwise the network's two-week timer will restart.
XRPL validator Vet has urged node operators to update their software before activation so their infrastructure remains compatible with the amended protocol. Operators using unsupported versions can become amendment-blocked once new rules go live, preventing their servers from determining the valid state of the ledger.
The $XRP Ledger community is working through multiple bug reports related to xrpld v3.2.0, with the problems posted on the XRPLF GitHub spanning from performance regressions to synchronization issues, despite node operators' ongoing migration to the latest release.
Among the more serious reports, a node operator stated that a server running xrpld v3.2.0 failed to synchronize with the XRP Ledger network, remaining stuck in a connected state without downloading ledger data, while the same machine successfully synchronized after downgrading to version 3.1.3.
Other open reports on the GitHub issue tracker include peer communication issues, resource charging rules, message parsing policies, message compression, consensus-related routing rules, and amendment processing. Additionally, some Windows 10 node operators report that their nodes never progress beyond the connected state despite stable peer connections.
To date, none of the documented bugs have triggered a complete network shutdown. The XRP Ledger Foundation, alongside open-source community contributors, is examining all submitted reports via the project's GitHub repository.
With less than 48 hours until the amendment is due to activate, the pressure is on developers to close out the remaining issues and ensure node operators are running compatible software before the deadline.
Sources:crypto.news: XRP Ledger pushes v3.2.0 rollout as amendment deadline nearsCoinGape: XRP Ledger 3.2.0 Upgrade: Community Flags Major Bugs In New Core ServerXRPL.org: Introducing XRP Ledger version 3.2.0
