Security warning (consensus issue) | Ethereum Foundation Blog

This warning is related to a consensus issue that occurred in block 116,522 of the Frontier network mined on 2015-08-20 14:59:16+02:00. Problem solved. See “Modification” below.

effect: High

Problem Description: Possible deletion of accounting data during the SUICIDE command causes a state database consensus issue in geth.

Implementations affected: All geth implementations including versions 1.0.1, 1.1.0 and develop (“Unstable 1.1.0”) has been affected. Eth (C++) and pyethereum (Python) are not affected.

Impact on expected chain reorganization depth: Increase final block confirmation waiting time to 12 hours.

Suggested workaround: Miners will switch to eth or pyethereum as soon as possible.

Improvement measures taken by Ethereum: We provide corrections below.

fix: Please note that the consensus issue arose just before the new release 1.1.0 was released. When upgrading, make sure to upgrade to the version you intended, as you may not want to make any changes. and At the same time, it will be upgraded from 1.0.1 to 1.1.0 (not yet officially released). The fixes below are for version 1.0.2. The build is produced for v 1.0.2.

• You can find release 1.0.2 including source and binaries. here
• If building from source: run git pull followed by make geth. Use master branch commits. a0303ff4bdc17fba10baea4ce9ff250e5923efa2
• If you’re using a PPA: sudo apt-get update Then sudo apt-get upgrade
• We are still working on the next one. decorate fix

The correct version for this update on Ubuntu and OSX is Geth/v1.0.2-.a0303f

After your coworker updates his or her client, you’ll likely receive the following message alert, which will resolve automatically some time later.

I0820 19:00:53.368852 4539 chain_manager.go:776) bad block it #116522 (05bef30ef572270f654746da22639a7a0c97dd97a7050b9e252391996aaeb689)

I0820 19:00:53.368891 4539 chain_manager.go:777) establish known bad hashes In ~ chain 05bef30ef572270f654746da22639a7a0c97dd97a7050b9e

update:

• 20/08/15 17:47+02:00 The issue has been identified and a fix is ​​in progress for geth. Geth(Go)-miners should upgrade and switch to Eth(C++) or Python as soon as a fix becomes available. Eth (C++) and Python miners are not affected.
• 20/08/15 19:38+02:00 See above for the official release of the fix.
• 20/08/15 21:19+02:00 The consensus issue occurred shortly before the announcement of the new release 1.0.2. So make sure you get the fix you want. That is, either stay at 1.0.1 or upgrade to 1.0.2. See “Edit” for more information.
• 15/08/21 11:30+2:00 We have been closely monitoring the chain and network since the consensus issue arose. According to network statistics, most miners have either upgraded to patch 1.0.2 or switched to eth. Our expectation for the maximum possible chain reorganization depth is 750 blocks.