XRP Ledger Server Upgrade Causes Multiple Bugs as Adoption Remains Low
Project maintainers are triaging confirmed sync, parser, consensus bugs to prevent upgrade-driven consensus problems.
Overview
- The xrpld v3.2.0 server was released on June 15 and advertised large memory and performance gains, but early adopters reported multiple faults within days of the rollout.
- Developers logged defects on GitHub that include nodes failing to download ledgers, a legacy configuration parser crashing on inline comments, and transaction relay logic that can under-relay transactions to peers.
- One operator reported a node upgraded to v3.2.0 that stayed “connected” but did not sync and only recovered after downgrading to v3.1.3, showing a practical risk for validators and exchanges performing live upgrades.
- Only about 26% of network nodes have upgraded so far, leaving a mixed-version network that increases the chance of upgrade coordination problems for validators and node operators.
- Maintainers have marked several reports as confirmed bugs and are assigning fixes through the public GitHub process, and they say none of the issues have caused a network-wide outage so far.