This alert is related to a consensus issue that occurred on the Frontier network at block 116,522, mined on 2015-08-20 at 14:59:16+02:00 – The problem has been fixed, see “Fix” below.
Impact: High
Description of the problem: Geth state database consensus issue with deletion of account data, which could occur during SUICIDE instructions.
Affected Implementations: All geth implementations up to and including versions 1.0.1, 1.1.0, and develop (“unstable 1.1.0”) were affected. Eth (C++) and pyethereum (Python) are not affected.
Effects on the expected depth of chain reorganization: Increase the waiting time for eventual block confirmation to 12 hours
Proposed workaround: Miners switch to eth or pyethereum ASAP
Corrective Action Taken by Ethereum: Provision of arrangements as shown below.
Arrange: Note that the consensus issue occurred just before the announcement of the new version 1.1.0. When upgrading, be sure to upgrade to the version you intended, as you may not want to fix Y upgrade from 1.0.1 to 1.1.0 (which hasn’t been officially released yet) at the same time. The fixes below are for version 1.0.2: Builds are generated for version 1.0.2.
- Version 1.0.2 can be found, including source and binaries here
- If you are building from source: git pull followed by make geth; use master branch commit a0303ff4bdc17fba10baea4ce9ff250e5923efa2
- If you use the PPA: sudo apt-get update after sudo apt-get update
- We are still working on it brew beer arrange
The correct version for this update on Ubuntu AND OSX is Geth/v1.0.2-a0303f
Please note that you will likely receive the following alert message which will resolve itself after some time once your colleagues have updated their clients:
I0820 19:00:53.368852 4539 chain_manager.Go:776) Bad to block #116522 (05bef30ef572270f654746da22639a7a0c97dd97a7050b9e252391996aaeb689)
I0820 19:00:53.368891 4539 chain_manager.Go:777) found known bad hash in string 05bef30ef572270f654746da22639a7a0c97dd97a7050b9e
Updates:
- 08/20/15 17:47+02:00 The problem has been identified and the geth problem is being fixed. Geth(Go)-Miners should upgrade as soon as possible once fixes become available and switch to Eth (C++) or Python in the meantime. Eth (C++) and Python miners are not affected.
- 08/20/15 19:38+02:00 Official release of fixes, see above.
- 08/20/15 21:19+02:00 Please note that the consensus issue occurred just before the announcement of the new version 1.0.2. So make sure you get the solution you want, ie stay on 1.0.1 or upgrade to 1.0.2. See “Repair” for more details.
- 08/21/15 11:30+2:00 Ever since the consensus issue occurred, we have been closely monitoring the chain and network. According to the network statistics, most of the miners either upgraded to the patched 1.0.2 or switched to eth. Our expectations regarding the probable maximum depth of reorganization of the chain is 750 blocks.
