Key Takeaways:
- XRPL developers identified four bug reports in xrpld v3.2.0 on GitHub
- Only 59.7% of nodes have upgraded ahead of the July 29 deadline
- The fixCleanup3_2_0 amendment has 85.7% validator support, above the 80% threshold
Back
XRPL v3.2.0 faces 4 bug reports as July 29 upgrade deadline nears
XRP Ledger developers are tracking four bug reports in xrpld v3.2.0, with the fixCleanup3_2_0 amendment set to activate July 29. The issues, posted on the XRPLF GitHub, range from performance regressions to synchronization failures that prevent nodes from reaching consensus.
"Happy Hump Day to everyone, especially those who have upgraded their XRP Ledger nodes to 3.2.0," XRPL validator Vet said on X. "In less than one week all nodes running XRPL versions below 3.2.0 will experience service interruptions. Please update your nodes, remind exchanges and projects to update as well."
According to XRP Ledger Explorer, 499 of 843 nodes, or 59.7%, are running version 3.2.0, while 303 nodes, or 36.2%, remain on version 3.1.3. Validator adoption has reached 65.8%, with 98 validators upgraded. The reported bugs include a performance regression where nodes gradually fall behind the validated ledger after upgrading from v3.1.3, a Windows 10 issue where nodes never progress beyond the "connected" server state, a validator that cannot download ledger data from peers, and a public key mismatch between validator services and server_info output.
The fixCleanup3_2_0 amendment currently has 30 of 35 trusted validators in support, or 85.7%, keeping it above the 80% activation threshold. If support holds, the amendment will activate on July 29 at 09:57 UTC. Nodes running versions below 3.2.0 face service interruptions after that date, putting pressure on the remaining 36.2% of operators to upgrade despite the unresolved bugs.
This article is for informational purposes only and does not constitute investment advice.
