The transition of the State and the problem of consensus in Geth Client cause panic (crash) when processing a block (valid) with a specific combination of transactions, which can cause the overall instability of the network if the block is accepted and relayed by unconceived customers, thus causing a back. This can happen in a block which contains transactions that commit suicide to the block reward address.
Assigned configurations: Related from Geth. When studying the question, related problems were discovered and corrected in Pyethereum, therefore Pyethapp is also affected. C ++ customers are not affected.
Probability: Weak
Severity: High
Complexity: High
Impact: Network instability and back
Details: A block containing a specific combination of transactions which include one or more suicide calls, although valid, causes a panic crash in the Go-Etherum client and a crash in Pyethereum. Additional details can be published when available.
Effects on the depth of reorganization of the expected chain: None.
Repair actions taken by Ethereum: Provision of fixes as below.
Temporary solution proposed: Go to an unassigned customer such as ETH (C ++).
Fix:Improve the Geth and Pyethereum customer software.
Go-Ethereum (Geth):
Please note that the current stable version of Geth is now 1.1.1; If you use 1.0 and use a package manager such as Apt-Get or Homebrew, the customer will be upgraded.
If you use the PPA: Update Sudo Apt-Get SO Sudo ApT-Get Angrade
If you use Brew: to update SO Ethereum Reinstalle Infusion
If you use a Windows binary: Download the binary update.
If you build from the source: git monitoring generate (Please use the master branch commit 8F09242D7F527972ACB1A8B2A61C9F55000E955D)
The correct version of this update on Ubuntu and Osx is Geth / V1.1-8F09242D
Pyethereum:
Pyethapp users should reinstall
> Pip Install Pyethapp – Force -Reinstall
