BitcoinHD 2.1.0.70 pre-release

Notice

• The blockchain of this version will be reset, and the block will start from height 20000. In order to speed up the synchronization, you can download bhd-testnet3-200000.zip in the attachment and unzip it in your data file directory.

• Please be sure to configure the official timelord server in Miner's config: timelord.bhd.one:19191, refer to the configuration example below.

• Plot's filter is reset to 0, please reduce the number of files to be mined to prevent excessive disk IO. In the official version, it will be changed to 9 like chia (filter=9)

• In the testnet3, K can be supported to a minimum of 25, just for the convenience of testing, and the minimum value of k in the mainnet is 32 for sure.

• The pre-release version will no longer provide macOS packages, and it will be provided in the official version.

Add timelord server configuration to the configuration file

Below is an example configuration of configuring timelord in config.json:

{
...
     "timelords": [
         "timelord.bhd.one:19191"
     ]
}

Improvements and Bug fixes

Adjustments to the consensus protocol

1. The Quality of Pos is only calculated and displayed in the Miner log.

2. The difficulty adjustment algorithm has been revised to avoid the frequency of new block caused by difficulty fluctuations.

Crash fix when Miner fails to connect to timelord

When the timelord connection was lost, the reconnection would cause a crash, this has been fixed.

Display the vdf speed and the estimated time to get the answer in the log in the Miner

Because different answers correspond to different answer acquisition times, the faster the acquisition time, the better the quality of the answer, which can now be displayed in the Miner log.

UpdateTip log display content update

Shows the speed of vdf, the amount of calculation of the total vdf iterations, the difficulty value and the k (file size) value of the plot

The minimum speed of vdf is no longer limited in the consensus protocol to prevent the problem that blocks cannot be generated after extreme situations occur

In the first block, the difficulty adjustment may cause the problem of excessive calculation error of vdf. In fact, it is not because the speed of vdf is too slow, but it may lead to the inability to produce blocks.

Algorithm adjustment for the best answer

Difficulty will be the only constant standard for the answer, and its value is displayed in Miner and UpdateTip.

When the private key does not match the plot file, the relevant plot file path will be displayed in the log

Delete some unnecessary P2P network packets to reduce the use of network bandwidth