Key facts
- New bug reports detail performance regressions and synchronization issues with XRP Ledger's v3.2.0.
- Some nodes are unable to sync or track the network after upgrading to v3.2.0.
- Validators are facing challenges downloading ledger data from peers.
- A mismatch in validator public keys has been identified.
- Node operators are warned of service interruptions if they do not upgrade by July 29.
- The fixCleanup3_2_0 amendment requires 80% validator support to activate on July 29.
The XRP Ledger (XRPL) community is addressing multiple bug reports concerning the xrpld v3.2.0 software, with an upcoming deadline of July 29 for the implementation of the fixCleanup3_2_0 amendment. Issues reported on the XRPLF GitHub include performance regressions where nodes lag behind the mainnet consensus, a problem that is resolved by reverting to the v3.1.3 version.
Further problems with v3.2.0 involve nodes on Windows 10 failing to sync beyond a 'connected' server state, despite having numerous peers and trusted validators. Similarly, mainnet validators are reportedly unable to download ledger data from peers and remain stuck in the 'connected' state. The process of acquiring the ledger on v3.2.0 is also noted as being slower than on v3.1.3. Additionally, a validator-related issue shows a mismatch between the new validator's public key and the one displayed in server information.
Amidst these concerns, XRPL validator Vet has encouraged users to upgrade to v3.2.0, warning of service interruptions for nodes running older versions after July 29. As of the report, 59.69% of nodes and 65.77% of validators are running v3.2.0. The fixCleanup3_2_0 amendment has garnered 85.71% support from trusted validators and is scheduled to activate on July 29, provided it maintains over 80% support.