Qitmeer Network Node Update: Optimized and Upgraded Network Performance

To all of our valued users,the latest version of the QNG node (qng-1.0.18+release-6ed3cd2) has been officially released, this upgrade is to optimize and improve memory usage,DAG algorithm, P2P network synchronization,qx tools, and focus on solving EVM memory overflow (OOM) issues in earlier versions.

Latest node access:

• Download release version

https://github.com/Qitmeer/qng/releases/tag/v1.0.18

• Source code compilation

～ git clone https://github.com/Qitmeer/qng.git

～ git checkout release/1.0.18

～ make

QNG version 1.0.18+release-6ed3cd2

QNG-1.0.18+release New Features

• Memory usage has been optimized, memory consumption has been decreased from 100% to 400%.
• DAG algorithm optimization and consensus are improved.
• Mining optimization to speed up packing efficiency and reduce empty block rate.
• P2P network and block synchronization optimization to improve synchronization efficiency.
• Optimized account manager.
• Improved qx command line tools and added compiled qx tools to the qng release package.
• Added analysis support of qng nodes.

Note: In qng-1.0.18+release, memory usage is optimized to reduce the node workload, and the “cachesize” value is set to 2000 by default. If your node has 8GB or more memory, we advise setting a larger “cachesize” value for better performance, e.g. — bdcachesize 20000 — dagcachesize 20000 . However, it is not always better to set a larger value but to consider the hardware situation. For 8GB nodes, the recommended configuration is 20000.

Bug Fix

• A memory leak in the go-Ethereum EVM cache may cause QNG to suffer an OOM crash. This issue has been fixed in the new version.
• Fixed a Panic error when using the ‘generate’ argument.
• Fixed the problem of command line arguments do not support ‘–acctmode’.
• Fixed the bug in the process of compiling, signing, and decoding transactions by qx command.
• Fixed the problem that stops synchronization when rescanning a reorg block.
• Fixed the problem of not using the state locker for DAG parents and children.
• Fixed the error of multithreaded checking of blue blocks and maturity.
• Fixed the problem of block synchronization panic caused by multi-threaded locker.
• Fixed the problem of not being able to exit during the db upgrade.

Development Plans

QNG-1.0.18+release will run as a long-term stable version. The next major release cycle will be QNG-1.1, which will include certain major changes, including the redeployment of the test network, upgrading of the chainID of the test network, and testing of new data structures and new features.