This alert is linked to a consensus problem on the border network in block 116 522, extracted on 2015-08-20 to 14: 59: 16 + 02: 00- The problem was solved, see “correction” below.
Impact: High
Description of the problem: Consensus problem of the state database in GTH with the deletion of account data, which could occur during suicide instructions.
Affected implementations: All GETH implementations until and including versions 1.0.1, 1.1.0 and develop (“Unstable 1.1.0”) have been affected. ETH (C ++) and Pyethereum (Python) are not affected.
Effects on the depth of reorganization of the expected chain: Increase the waiting time for a possible confirmation of blocks to 12 hours
Temporary solution proposed: Minors go to Eth or Pyethereum as soon as possible
Repair actions taken by Ethereum:: Provision of fixes as below.
Fix: Note that the consensus problem occurred just before the announcement of the new version 1.1.0. When upgrading, be sure to go to the version you had planned because you may not want to repair And Upgrade from 1.0.1 to 1.1.0 (which has not yet been officially published) at the same time. The fixes below are for version 1.0.2 – The builds are generated for V 1.0.2.
- Version 1.0.2, including the source and the binarys can be found here
- If you build from the source: Git sweater followed by Make Geth – Please use the Master Commit branch A0303FF4BDC17FBA10BAEA4CE9FF250E5923EFA2
- If you use the PPA: Update Sudo Apt-Get SO Sudo ApT-Get Angrade
- We are still working on the brew fix
The correct version of this update on Ubuntu and Osx is Geth / V1.0.2-A0303F
Note that it is likely that you will receive the following message alert which will be resolved after a while once your peers have updated their customers:
I0820 19::00::53.368852 4539 chain_manager.go::776)) Bad block # 116522 (05BEF30EF572270F654746DA22639A7A0C97DD97A7050B9E252391996AAEB689)
I0820 19::00::53.368891 4539 chain_manager.go::777)) Find bad hatching In chain 05BEF30EF572270F654746DA22639A7A0C97DD97050B9E
Updates:
- 08/20/15 17: 47 + 02: 00 The problem has been identified and a correction for Geth is underway. Geth (Go) -mine should upgrade as soon as possible once the fixes are available and in the meantime, go to ETH (C ++) or Python. ETH (C ++) and Python minors are not affected.
- 08/20/15 19: 38 + 02: 00 Official release of fixes, see above.
- 08/20/15 21: 19 + 02: 00 Note that the question of consensus occurred just before the announcement of the new version 1.0.2. Therefore, please make sure you get the correction you want, that is, stay on 1.0.1 or go to 1.0.2. See “Fix” for more details.
- 08/21/15 11: 30 + 2: 00 Since the occurrence of the problem of consensus, we closely monitor the chain and the network. According to network statistics, most minors have upgraded to the 1.0.2 or Eth fixed chest. Our expectations concerning the maximum depth of reorganization of the probable chain are 750 blocks.
Source link
post url: https://altcoin.observer/security-alert-consensus-number-ethereum-foundation-blog/
16,573
Lunam Points