This happened while setting up cpp-ethereum (actually reinstalling via brew, because nondevelop version uses old protocol). As a result some estimated 60 ethers lost from ming x2 blocks. I will later look up the account number, just noted that among the blocks were #298407 and #298439. They were mined on 6-core system, so almost every 50th block could be mined in pre-GPU days.
I tried to reproduce the removal of the keystore folder but apparently current state is different and has no effect. This is a sequence fragment from .bash_history
brew reinstall cpp-ethereum --devel
eth -V
brew install cpp-ethereum --devel
brew reinstall cpp-ethereum --devel
brew tap ethereum/ethereum
brew tap cpp-ethereum
brew reinstall cpp-ethereum --devel
brew reinstall cpp-ethereum
brew reinstall cpp-ethereum --devel
brew doctor
brew update
brew doctor
brew update node
brew upgrade ethereum/ethereum/cpp-ethereum
brew upgrade ethereum/ethereum/ethereum
eth -V
brew reinstall cpp-ethereum --devel
eth -V
brew reinstall cpp-ethereum --devel
pwd
eth -m on --listen 30301
eth -h
eth -K
eth -K -m on --listen 30301
eth -R -m off --listen 30301
eth -R --listen 30301
eth -R --listen 30311
brew linkapps cpp-ethereum
If anyone can make out any sense of this, please let me know. It would be great to know the best method to update these clients.
And yes, wallets have to be backed up even on testnet.
0 ·
Comments
I had mined 80 blocks with CPU. Address: eb55a10171a9784caa953ae7da5a75d8eb59099a
Nowadays (2 days later) GPUs totally have taken over and 6 cores can barely yield estimated 5 - 10 blocks a day.
I have upgraded to geth 0.9.20 then I try to create a new account by importing my old private key and after filed the password I have this as a result:
Fatal: Could not create the account: encoding/hex: invalid byte: U+007B '{'
Fatal: Could not create the account: encoding/hex: invalid byte: U+007B '{'
I'm sure I fucked up somewhere between the back up of my old key and upgrated the geth software
Create a new address, export it and then compare this new one with your old un-importable one.
Maybe you will see some pattern, missing characters, etc. Preferably make it a binary comparison.
While experimenting I could reproduce the error you reported. To reproduce I executed these steps:
1. Create new account
2. Copy it
3. Remove it
4. Restore from copy
Here is the console:
Is this how you got this error?
geth account import
tool. You can simply copy over the entire file to the new keystore folder.See
geth help (topic)
for help about the specific commands.could not unlock signer account
at InvalidResponse (:-59655:-133)
even though it's my password.