Implementation bug within the go consumer results in regular improve of problem impartial of hashing energy.
Affected configurations: All Go consumer variations v1.0.x, v1.1.x, launch and develop branches. The bug was launched in a latest replace and launch via commit https://github.com/ethereum/go-ethereum/commit/7324176f702a77fc331bf16a968d2eb4bccce021 which went into the affected consumer variations. All miners operating earlier talked about variations are affected and are suggested to replace as quickly as attainable.
Probability: Excessive
Severity: Medium
Impression: Improve in block time will result in an exponential improve in problem
Particulars: A bug within the go consumer results in regular improve in problem within the following block, as timestamp in new block = timestamp + 1 of outdated block, whatever the precise time, when mining. This results in a rise within the problem independently of the hashing energy
Results on anticipated chain reorganisation depth: None
Proposed short-term workaround: None
Remedial motion taken by Ethereum: Provision of hotfixes as under:
If utilizing the PPA: sudo apt-get replace then sudo apt-get improve
If utilizing brew: brew replace then brew reinstall ethereum
If utilizing a home windows binary: obtain the up to date binary from the release page
In case you are constructing from supply: git pull adopted by make geth (please use the Grasp department 587669215b878566c4a7b91fbf88a6fd2ec4f46a)