Note that this is likely dangerous and you shouldn't do it It currently take 9+ hours to completely reprocess the testnet blockchain when downloading it from scratch via Geth. This has almost nothing to do with download speeds - instead, it's the time it takes to import each block and validate them that's the culprit. And the chain is big, very big - because we encouraged the Olympic phase users to push as many transactions as possible on a network where gas is in effect, free.
For this same reason, if you try to geth export, then geth import the testnet chain, you'll find it doesn't save time either.
So, is there a solution when you're in a rush? Well, kind of. If you simply overwrite your chain directory with one from a client that is already up to date, geth seems quite content to accept it and simply pick up from where the other client left off.
Now, please note this is really a non-solution: the chain I'm making available here as a download could have been messed with, its data modified to the uploader's advantage (me). I can only give you the SHA1 for the file and hope a middleman won't rewrite my post and link to a corrupt file, for example.
I had a brief chat with Jeffrey about this and we agreed that if we were to one day distribute the chain this way, it would likely be over Swarm (our decentralized storage layer, currently in development), and several failsafes would be in place to help prevent forgeries.
However, I understand that the recent stress test has made it difficult to reimport the more recent blocks, and until a fix is out, well, overwriting the chain will save some of you several hours. It's a also a nice little test of what might become 'a thing' if it gets automated (with the SHA1 posted on as many of our 'out of band' channels as possible).
So, without further ado, here's a link to thetestnet chain as of yesterday, July 10th 2015. It was extracted from ~/.ethereum on OSX, but should be compatible wiht any Geth RC1+ install.
https://mega.co.nz/#!zkkzSS5B!gQxT0Ke8dp-Geso1QMWRqZQ5OUfselKkhPQizXwxdkQFeedback would be great!
Cheers!
Comments
This way there would be a SHA1 of every 30,000 blocks on the ethereum blockchain and it would be easy to verify torrents with a simple tool.
EDIT: I just realised you would need access to others with a trustworthy chain to compare the SHA1 too. But I guess that's the case with any solution
I have these files on Widnows 8:
...appdata\roaming\ethereum\...
Where does this go?
\blockchain
\extra
\keystore
\nodes
\state
history
nodekey
I just copy-paste? if so, where?
Thx!
I've found some scripts that claim to download from Mega from the CL but they aren't working.
but could we please go back to the torrent, or put the file on amazon s3 and spend a few bucks on the community, this mega thing is not for anything but a browser and even then the fact that i have to decrypt this file after is a waste of time
Note that I didn't take down the Torrent, it's still running on my seedbox. However it's outdated. I attach the torrent file to this post.
If I get a chance I'll seed the new one.
The Mega file is listed at 42.1 GB
Upon downloading and unzipping it, 'du -sh' counts 5.9 GB for the 3 directories. Compression ratio < 1 ??
Something else, Chromium's local storage was limited to 10 GB so the huge Mega download failed. Megatools worked very well downloading it directly without a GUI.
I have a question, this download concern only the geth client, not the eth client.
And in my memory, i guess that it is incompatible between the two clients, so i can't use this blockchain with the eth client, and i'm still stuck with this error with the eth client :
https://forum.ethereum.org/discussion/2926/guru-meditation-on-olymic-network
How can i solve this problem and hope my rewards ?
Thanks
Jérémie.