This alert is expounded to a consensus subject that occurred on the Frontier community at block 116,522, mined on 2015-08-20 at 14:59:16+02:00 – Situation has been mounted, see “Repair” beneath.
Influence: Excessive
Situation description: State database consensus subject in geth with deletion of account information, which may 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”) have been affected. Eth (C++) and pyethereum (Python) are unaffected.
Results on anticipated chain reorganisation depth: Enhance ready time for eventual block affirmation to 12 hours
Proposed momentary workaround: Miners swap to eth or pyethereum asap
Remedial motion taken by Ethereum: Provision of fixes as beneath.
Repair: Notice that the consensus subject occured simply earlier than the announcement of the brand new launch 1.1.0. When upgrading, please ensure you improve to the model you supposed as you may not wish to repair and improve from 1.0.1 to 1.1.0 (which has not but been formally launched) on the identical 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 could be discovered right here
- If you’re 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
Notice that it’s seemingly that you just obtain the next message alert which can 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] Unhealthy block #116522 (05bef30ef572270f654746da22639a7a0c97dd97a7050b9e252391996aaeb689)
I0820 19:00:53.368891 4539 chain_manager.go:777] Discovered recognized dangerous hash in chain 05bef30ef572270f654746da22639a7a0c97dd97a7050b9e
Updates:
- 20/08/15 17:47+02:00 Situation has been recognized and repair for geth is underway. Geth(Go)-Miners ought to improve asap as soon as the fixes change into obtainable and in the meantime swap 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 Notice that the consenus subject occured simply earlier than the announcement of the brand new launch 1.0.2. Subsequently, please ensure 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 For the reason that prevalence of the consensus subject, we have been carefully monitoring the chain and community. In line 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.