This alert is said to a consensus situation that occurred on the Frontier community at block 116,522, mined on 2015-08-20 at 14:59:16+02:00 – Problem has been mounted, see “Repair” beneath.
Impression: Excessive
Problem description: State database consensus situation in geth with deletion of account knowledge, which might occur throughout SUICIDE directions.
Affected implementations: All geth implementations as much as and together with variations 1.0.1, 1.1.0 and develop (“unstable 1.1.0”) had been affected. Eth (C++) and pyethereum (Python) are unaffected.
Results on anticipated chain reorganisation depth: Improve ready time for eventual block affirmation to 12 hours
Proposed momentary workaround: Miners change to eth or pyethereum asap
Remedial motion taken by Ethereum: Provision of fixes as beneath.
Repair: Observe that the consensus situation occured simply earlier than the announcement of the brand new launch 1.1.0. When upgrading, please be sure you improve to the model you supposed as you won’t wish to repair and improve from 1.0.1 to 1.1.0 (which has not but been formally launched) on the similar time. Fixes beneath are for model 1.0.2 – builds are generated for v 1.0.2.
- Launch 1.0.2 together with supply and binaries might be discovered here
- In case you are constructing from supply: git pull adopted by make geth – please use the grasp department commit a0303ff4bdc17fba10baea4ce9ff250e5923efa2
- If utilizing the PPA: sudo apt-get replace then sudo apt-get improve
- We’re nonetheless engaged on the brew repair
The proper model for this replace on Ubuntu AND OSX is Geth/v1.0.2-a0303f
Observe that it’s seemingly that you just obtain the next message alert which is able to resolve itself after some time as soon as your friends have up to date their purchasers:
I0820 19:00:53.368852 4539 chain_manager.go:776] Dangerous block #116522 (05bef30ef572270f654746da22639a7a0c97dd97a7050b9e252391996aaeb689)
I0820 19:00:53.368891 4539 chain_manager.go:777] Discovered identified unhealthy hash in chain 05bef30ef572270f654746da22639a7a0c97dd97a7050b9e
Updates:
- 20/08/15 17:47+02:00 Problem has been recognized and repair for geth is underway. Geth(Go)-Miners ought to improve asap as soon as the fixes turn into accessible and in the meantime change to Eth (C++) or Python. Eth (C++) and Python miners are unaffected.
- 20/08/15 19:38+02:00 Official launch of fixes, see above.
- 20/08/15 21:19+02:00 Observe that the consenus situation occured simply earlier than the announcement of the brand new launch 1.0.2. Subsequently, please be sure that you get the repair you need, i.e. stay on 1.0.1 or improve to 1.0.2. See “Repair” for extra particulars.
- 21/08/15 11:30+2:00 Because the incidence of the consensus situation, we have been intently monitoring the chain and community. In accordance with community statistics, most miners have upgraded to the patched 1.0.2 or switched to eth. Our expectations regarding most seemingly chain-reorganization depth is 750 blocks.
