Security alert [consensus issue]

KenK

This alert is related to a consensus issue that occurred on the Frontier network at block 116,522, mined on 2015-08-20 at 14:59:16+02:00

Impact: High

Issue description: Edge case in the Go implementation of the consensus protocol for contract suicides

Affected implementations: All implementations of Geth (Go). Eth (C++) and pyethereum (Python) are unaffected

Effects on expected chain reorganisation depth: Increase waiting time for eventual block confirmation to 12 hours

Proposed temporary workaround: Miners switch to eth or pyethereum asap

Remedial action taken by Ethereum: TBD

Fix: TBD

Updates:

17:47+02:00 Issue has been identified and fix for geth is underway. Geth(Go)-Miners should upgrade asap once the fixes become available and meanwhile switch to Eth (C++) or Python. Eth (C++) and Python miners are unaffected.
We will post an update in 30 min

juttasteiner

We are distributing updates in all channels (blog, forum, twitter, IRC, etc.) asap. Earliest updates will be given on blog.ethereum.org.

Escalicha

I'm waiting for an update.

Thanks

acros

@Escalicha an update has been posted on the blog: https://blog.ethereum.org/2015/08/20/security-alert-consensus-issue/

evan

how likely is it that we will return to the bad block?

juttasteiner

All transactions mined by geth after block 116,522 should be considered unconfirmed.

juttasteiner

Issue description: Edge case in the Go implementation of the consensus protocol for contract suicides
Affected implementations: All implementations of Geth (Go). Eth (C++) and pyethereum (Python) are unaffected
For earliest updates: See blog.ethereum.org or https://blog.ethereum.org/2015/08/20/security-alert-consensus-issue/

Righteous

I'm assuming this is why my eth(c++) has been throwing "block hash bad" and "InvalidReceiptsStateRoot" errors?

acros

how many blocks are poloniex and kraken using for confirmation?

urwald

am I ok by mining with Geth-v1.0.3 ? I'm the node 'urwald'...

heaveancorner

what to do if we are not concerned? restart geth ? rebuilt the blockchain etc ???

acros

@urwald and @heaveancorner , I would avoid mining and potentially further confirming double-spent ether (provided there has been any)

urwald

ok ! I'm not mining now, just run as passive node... Somebody could publish the right version of Geth to use, when avalaible ?

juttasteiner

We will publish fixes for geth once they become available. The issue has been identified, but we are waiting for tests to confirm.
Meanwhile, all geth (Go) miners should either stop or better switch to eth (C++) or pyethereum (Python).