mist
mist copied to clipboard
Ethereum Wallet 0.9.2 downloads geth 1.6.6 NOT 1.7.2, thus rolls back chain to block 4370000
Hi. Looks like the latest Ethereum Wallet v0.9.2 (at least on windows x64) will download for itself geth 1.6.6 (if there is no geth node already running). The 1.6.6 geth will then reset the chain data to block 4370000 (even though the chain is ahead having been run forward on geth 1.7.2). When geth 1.7.2 is then started on the command line, it resets the chain again to get onto the Byzantium branch.
I don't see a way to choose a geth version within the Ethereum Wallet v0.9.2.
Solution: release a new version of Ethereum Wallet that defaults to geth 1.7.2 and thus the byzantium release.
Thank you.
Ludo
- [NO ] I've asked for help in the Mist Gitter before filing this issue.
Version: `0.9.2`
OS & Version: windows
Node version: `geth 1.7.2` (in windows)
Number of blocks synchronized: 4466116 but getting reset back to 4370001 when opening wallet
Im having the exact same bad block problems with block 4370000. i am unable to use ETH stuck in my wallet for several weeks now. This error occured shortly after updating to v9.2, i agree there is an fix required.
update: sitation resolved with installation and use of EthWallet 9,3. thanks developers!
@LudoTheHUN @jimbnz
Can you please provide the file %APPDATA%\Mist\clientBinaries.json
?
It doesn't contain any personal information. This is the node manifest, where Mist downloads geth from.
%APPDATA%\Mist\clientBinaries.json
does not point anywhere for me since I'm not using Mist. I have whoever %APPDATA%\Ethereum Wallet\clientBinaries.json
with this here below. I'm on a windows10 box. This clientBinaries.json file was last modified, 10 September 2017, so looks like it did not update as part of my upgrade of Ethereum Wallet, which is on v 0.9.2
{
"clients": {
"Geth": {
"version": "1.6.6",
"platforms": {
"linux": {
"x64": {
"download": {
"url": "https://gethstore.blob.core.windows.net/builds/geth-linux-amd64-1.6.6-10a45cb5.tar.gz",
"type": "tar",
"md5": "5d60910275bcdec0ddf6e9c217e65b9d",
"bin": "geth-linux-amd64-1.6.6-10a45cb5/geth"
},
"bin": "geth",
"commands": {
"sanity": {
"args": [
"version"
],
"output": [
"Geth",
"1.6.6"
]
}
}
},
"ia32": {
"download": {
"url": "https://gethstore.blob.core.windows.net/builds/geth-linux-386-1.6.6-10a45cb5.tar.gz",
"type": "tar",
"md5": "cf6794245871235a7664903090593479",
"bin": "geth-linux-386-1.6.6-10a45cb5/geth"
},
"bin": "geth",
"commands": {
"sanity": {
"args": [
"version"
],
"output": [
"Geth",
"1.6.6"
]
}
}
}
},
"mac": {
"x64": {
"download": {
"url": "https://gethstore.blob.core.windows.net/builds/geth-darwin-amd64-1.6.6-10a45cb5.tar.gz",
"type": "tar",
"md5": "faf0aa0af6d90685deeef70062d653f5",
"bin": "geth-darwin-amd64-1.6.6-10a45cb5/geth"
},
"bin": "geth",
"commands": {
"sanity": {
"args": [
"version"
],
"output": [
"Geth",
"1.6.6"
]
}
}
}
},
"win": {
"x64": {
"download": {
"url": "https://gethstore.blob.core.windows.net/builds/geth-windows-amd64-1.6.6-10a45cb5.zip",
"type": "zip",
"md5": "2a73767451a27538f3f335bf5d466658",
"bin": "geth-windows-amd64-1.6.6-10a45cb5\\geth.exe"
},
"bin": "geth.exe",
"commands": {
"sanity": {
"args": [
"version"
],
"output": [
"Geth",
"1.6.6"
]
}
}
},
"ia32": {
"download": {
"url": "https://gethstore.blob.core.windows.net/builds/geth-windows-386-1.6.6-10a45cb5.zip",
"type": "zip",
"md5": "08188b29b8f2ba49db52215cc279c23e",
"bin": "geth-windows-386-1.6.6-10a45cb5\\geth.exe"
},
"bin": "geth.exe",
"commands": {
"sanity": {
"args": [
"version"
],
"output": [
"Geth",
"1.6.6"
]
}
}
}
}
}
}
},
"swarm": {
"archives": {
"windows-amd64": {
"archive": "swarm-windows-amd64-1.6.7.exe",
"binaryMD5": "c2d827dc4553d9b91a7d6c1d5a6140fd",
"archiveMD5": "059196d21548060a18a12e17cc0ee59a"
},
"linux-amd64": {
"archive": "swarm-linux-amd64-1.6.7",
"binaryMD5": "85002d79b8ebc2d2f2f10fb198636a81",
"archiveMD5": "3e8874299ab8c0e3043d70ebb6673879"
},
"linux-386": {
"archive": "swarm-linux-386-1.6.7",
"binaryMD5": "35bc2ab976f60f96a2cede117e0df19d",
"archiveMD5": "7868a86c9cbdf8ac7ac2e5682b4ce40f"
},
"darwin-amd64": {
"archive": "swarm-darwin-amd64-1.6.7",
"binaryMD5": "c499b186645229260dd6ab685dd58f07",
"archiveMD5": "0794d111e5018eac3b657bcb29851121"
},
"linux-arm5": {
"archive": "swarm-linux-arm5-1.6.7",
"binaryMD5": "516fcd85246c905529442cd9b689c12f",
"archiveMD5": "47312708d417cb196b07ba0af1d3abb4"
},
"linux-arm6": {
"archive": "swarm-linux-arm6-1.6.7",
"binaryMD5": "82ff7bdbe388b4a190f4101c5150d3b4",
"archiveMD5": "350276de7bb175a15c314cfc4cb7f8fd"
},
"linux-mips": {
"archive": "swarm-linux-mips-1.6.7",
"binaryMD5": "e1e95280441c0ca35633927792ef5317",
"archiveMD5": "8fb4b64e94cd73aa718db787b9d4c53e"
},
"linux-arm7": {
"archive": "swarm-linux-arm7-1.6.7",
"binaryMD5": "bfc0b4d1c86d8a975af052fc7854bdd3",
"archiveMD5": "4378641d8e1e1fbb947f941c8fca8613"
},
"linux-arm64": {
"archive": "swarm-linux-arm64-1.6.7",
"binaryMD5": "bbac21a6c6fa8208f67ca4123d3f948a",
"archiveMD5": "4e503160327c5fbcca0414f17c54e5ee"
},
"linux-mipsle": {
"archive": "swarm-linux-mipsle-1.6.7",
"binaryMD5": "a82f191b2f9d2c470d0273219c820657",
"archiveMD5": "3016bdb6d237ae654c0cdf36fe85dc7c"
},
"windows-386": {
"archive": "swarm-windows-386-1.6.7.exe",
"binaryMD5": "ce0b34640642e58068ae5a359faef102",
"archiveMD5": "640aede4da08a3a9d8a6ac0434ba7c0f"
},
"linux-mips64": {
"archive": "swarm-linux-mips64-1.6.7",
"binaryMD5": "9da967664f384817adb5083fd1ffe8f1",
"archiveMD5": "357a33be470f8f89ba2619957a08deff"
},
"linux-mips64le": {
"archive": "swarm-linux-mips64le-1.6.7",
"binaryMD5": "ec1abcf7b216e87645ec83954d8344cd",
"archiveMD5": "a81fd0158190d99813c738ffa4f87627"
}
}
}
}
Thanks!
The 32-bit and 64-bit archives (v1.7.1, v1.7.2 and v.1.7.3) on the Geth download page for Windows seems to download version v1.3.3 instead. I am not sure where Mist is downloading the node from, but when I remove it and let Mist download it, I end up with the same version. My guess is that it is downloading from the same location, and that some people (myself included) have unknowingly ended up on the wrong side of the Byzantium chain split.
Downloading the Linux binary archive of Geth (64-bit) does give me the right version. So there is probably something wrong with the Windows build/packing/distribution service of Geth.
@jackvreeken My issue is specifically with Ethereum Wallet which seems to download and run the version of geth noteds in the json above "version": "1.6.6",
.
As an experiment, I went and deleted the %APPDATA%\Ethereum Wallet\clientBinaries.json file and ran the Ethereum-Wallet-installer-0-9-2.exe
installer. (I don't think this did anything, a new clientBinaries.json did not appear.
Running Ethereum Wallet.exe
however then regenerated the clientBinaries.json
file, which now references geth 1.7.2
{
"clients": {
"Geth": {
"version": "1.7.2",
...
So, while this does fix my issue. There is a problem in the installer in that it leaves behind the old config the json file, thus leaving some users (potentially unaware) that they are using a an old branch. I presume this will only affect users that upgraded from an older release.
I confirm this issue! I solved this issue deleting both geth.exe and clientBinaries.json to force update of geth. EVEN in the new version 0.93 of ethereum wallet (without installer)
0.9.3 still downloads 1.7.2 instead of 1.7.3 even if I delete both these files.
I am running 0.9.3 and it downloads 1.7.2 I don't know if this is linked but my mist wallet and my my ether wallet get stuck on the last 100 blocks. is there a fix for this as I cant access any of my Ether
@Cobbs95 You can use MyEtherWallet in the meantime to access your ETH.
@Cobbs95 try running the latest geth while/before you turn on the wallet.
@LudoTheHUN already tried running latest geth while and before I turned on my wallet. Also tried making the cache 1024 all stuck 300 blocks before....