This is now fixedEdited by @StephanTual Thursday 7pm GMT.This issue only affected geth users (or geth users in combination with ethminer). If you are using Geth, please update now.
To update:
If using the PPA:
sudo apt-get update
then
sudo apt-get upgrade
If using brew:
brew update
then
brew reinstall ethereum
If using a windows binary: download the
updated binary.
If you are building from source:
git pull
followed by
make geth
(you need to be on the Master branch)
The correct version for this update on Ubuntu AND OSX is Geth/v1.0.2-4591ae56 and v1.0.2-a0303f (both are fine)
On windows, the latest chocolatey package version is Geth Stable 1.0.1.2 and it's pulling from download/v1.0.1.2/Geth-Win64-20150820212541-1.0.1-f0c7af0.zip (this is normal)
Note, if you are getting:
I0820 19:00:53.368852 4539 chain_manager.go:776] Bad block #116522 (05bef30ef572270f654746da22639a7a0c97dd97a7050b9e252391996aaeb689)
I0820 19:00:53.368891 4539 chain_manager.go:777] Found known bad hash in chain 05bef30ef572270f654746da22639a7a0c97dd97a7050b9e
.. after updating this is NORMAL and will resolve itself once your peers have updated their clients, too.
UPDATE 10:52 BST: We have released a new update on the state of the network post consensus failure and expectations on chain reorganization depth (now 750 blocks)
https://blog.ethereum.org/2015/08/20/security-alert-consensus-issue/------------
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
Comments
Thanks
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/
Meanwhile, all geth (Go) miners should either stop or better switch to eth (C++) or pyethereum (Python).
n 05bef30ef572270f654746da22639a7a0c97dd97a7050b9e252391996aaeb689
I0820 20:26:14.347048 2840 downloader.go:254] Synchronisation failed: hash fe
tching canceled (requested)
Apparently i'm mining .
Seems like we really need to inform people not to pool mine at this stage of things.
working fine
And I will take the opportunity to desctibe my problem with poloniex...
I had sent a big sum of Ether's to poloniex before the security announcement and it made 333 confirmations... after that they freeze the transaction (pending) and disabled the wallet.... The strange thing is that they changed the confirmations to 204/3000 (instead of 333) and they changed the transaction time stamp for the same transaction with a difference of about 4 hours !!! The original transaction was made at 2015-08-20 14:53:58 and they changed the timestamp for the same transaction to 2015-08-20 18:40:12 (with the confirmation difference). Luckily I have screen-shot’s for what i am describing... has anybody a clue what could happen? Is there a possibility they want to hide something? I am really very frustrated with the situation.
Then again none of the above is different to what we provide the community (either in content or timing). What they do with that information is up to them.
> I0821 09:06:18.613480 5612 downloader.go:278] Block synchronisation started
I0821 09:06:20.660828 5612 chain_manager.go:660] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 1.1637769s. #115299 [6c03d6ad / 6c03d6ad]
I0821 09:06:20.664831 5612 chain_manager.go:776] Bad block #115300 (30ef297811617a9f246592fa57f2af23f61cbb74e2b793054a64b58532713df4)
I0821 09:06:20.664831 5612 chain_manager.go:777] Transaction w/ invalid nonce. tx=5349 state=0)
I0821 09:06:20.664831 5612 downloader.go:254] Synchronisation failed: block downloading canceled (requested)
I0821 09:06:29.645939 5612 chain_manager.go:660] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 5.012ms. #115299 [6c03d6ad / 6c03d6ad]
I0821 09:06:29.805415 5612 chain_manager.go:776] Bad block #115300 (30ef297811617a9f246592fa57f2af23f61cbb74e2b793054a64b58532713df4)
I0821 09:06:29.805415 5612 chain_manager.go:777] Transaction w/ invalid nonce. tx=5349 state=0)
I0821 09:06:29.806416 5612 downloader.go:254] Synchronisation failed: hash fetching canceled (requested)
Anybody help me?