XRPL developers are currently examining the software bugs that have been reported after the June 15 launch of xrpld version 3.2.0; however, only 26% of nodes have migrated to this version. Some of the bugs reported include synchronization issues, parsing errors, and network-related bugs in the software.
These reports have been posted in the GitHub repository of the XRP Ledger project since the June 15 release. The XRP Ledger maintainers have also categorized some of these reports as confirmed bugs and submitted for review. Other items were left open while contributors were still continuing to assess.
Also Read: XRP Ledger Stablecoin Market Reaches $907M With 84% RLUSD Share
XRP Ledger Node Fails to Sync After xrpld 3.2.0 Upgrade
The node operator stated that the server running version 3.2.0 of xrpld failed to fetch any ledger information, even though the server was able to connect to the peers.
The server continued to stay active in its connected state without synchronization. It has been found out that the same hardware could sync in version 3.1.3.
This bug has been recorded on GitHub on 18th June, and it is still open. This is an issue related to the configuration of only one node and does not indicate a wider network failure.
The other XRP Ledger-related matter concerned configuration file processing. It was found by a developer that comments made inline in certain fields can cause problems with server startup.
Due to the wrong processing by the legacy parser, which cannot process them properly from some fields and produces a BadLexicalCast error.
Other issues concerning peer connections, message compression, resource charges, amendments processing, message parsing, and routing were submitted by developers to project maintainers. Several filings marked as bugs and sent to contributors.
Transaction Relay and Validator Distribution Issues Emerge
In the XRP Ledger repository filing described a problem with transaction relay functionality. The calculation error in relayed transactions that limits the number of peers receiving this transaction. The filing described the resource charging system that keeps only the largest value of the fee and does not store previous ones.
Another matter submitted by developers concerned validator list distribution. It was pointed out that validator information is distributed only to inbound peers, not outbound connections.
The report does not make any connection to this activity to any disruption in the operation of the network. The problem is caused by an imbalance in the transmission of information to validators. Maintainability reports do not indicate a widespread impact on the network.
Submissions received after this one had focused more on validation functions and consensus activities in XRP Ledger software.
Validation Bugs Surface as xrpld 3.2.0 Review Continues
The submission indicated an overflow problem with ledger sequence and an inconsistency with routing flags for transactions. Another report has noted that the proposal node identifiers do not perform well when using ephemeral keys.
Prior to its deployment, the upgrade is expected to reduce memory utilization by 30% to 40%. In addition, it also includes performance improvements, increased security measures, and the renaming of the name of rippled to xrpld. These are all improvements that were discussed prior to the bug reports.
The XRP Ledger Foundation and project contributors are currently looking into the issue through the open-source development process. At present, the existing issues do not correspond to any outage in the operation of the network based on the current GitHub reports.
Also Read: European Union Introduces €10,000 Cash Limit Under New AML Rules
