I created a bootstrap for PayCon, the file is 76mb and takes approximately an hour and a half to reindex the whole Blockchain. This is useful for new users in that they can use the bootstrap and sync up their clients from first install much quicker.
For first install navigate to your data directory (appdata/roaming/PayCon for Windows, .PayCon for Linux), just have the bootstrap.dat, PayCon.conf and wallet.dat(optional) in this directory.
Open PayCond or PayCon QT, it will reindex the Blockchain and seem to hang but atleast 75% time savings on first install.
Let it finish and it will catch up once finished indexing.
Download:
https://mega.co.nz/#!DhVHEQiC!wY_e2gzCtVsHX8a3um6IFjAUdiNTlCYqGW46Ga-0KYw
bootstrap.dat file, created at Wed Jun 3 13:46:07 PDT 2015
sha256sum: 0cc0cfb3533ac15b5c0982e7d70432cdfd95bdc47d7c62267a9d28509eb00427
md5sum: 4cc330d826c8344b2806753e1414ba45
Verify before using it!
Thank you to Biomech and billotronic for the help
the end user would put the bootstrap into their datadir, start the client, the client processes the blocks, you save a shit ton of time vs syncing a virgin client. it is not the fastest thing in the world, but i would guess of the time savings at the very least 75%.
also, super sexy pi client just cooked for distro from sluppy can be found on the
release page check it out.
So you put it in the same directory as the Blockchain? If you have an existing Blockchain do you delete that? What is the reason of renaming it bootstrap.dat? Would it just not be easier to replace the Blockchain with another one and not have to rename it?
Congrats on the new pi client!!!Yes, you put it in (in this case) .hyperstake (or the windows/Mac equivalent) and then delete everything but wallet.dat, hyperstake.conf and bootstrap.dat
The reason for renaming it is that the core code looks for bootstrap.dat to import a static blockchain, and it imports the whole freaking thing before indexing it. That saves a shitload of time. The reason for not just copying the whole .hyperstake (or whatever coin) data directory is that the data may be corrupt, have transactions only specific to your wallet, etc. And of course, the size. Everything that is needed for the client to extract all that information is in the blk000* files. There are several of them as the blockchain grows, so if you're making a bootstrap AND there is more than one, you need to combine them in serial order. It's easy to do, and it will save you endless headaches when synching a new install or recovering a messed up wallet install.
Another thing I do, and highly suggest if you're not running on a Pi or something tiny like that is add txindex=1 to your configuration file. This pulls ALL the blockchain data, like a block explorer. so you can pull up the data from any valid block in the chain in your own client, not just the ones you had a transaction in
yeah what bio said! and I am almost 100% certain you should close the client before doing so. (I always do)
best part is with hyp since the blockchain is still small you can actually just rename blk0001.dat to bootstrap.dat or cat it like bio said if you wanted to make it nice and automated.
that is a feature press should put into his explorer.
https://ecua.mobi/how-to-create-bootstrap-dat/There ya go. I used it once, but didn't have a download directory setup. I do now, and once GMC is fixed, I'll be using this script to maintain a constantly updated bootstrap. Might do the same for all the coins I collect
Though that would require a bigger server than I have right now. At any rate, the script works with minimal modification, or you can just do it manually. You MIGHT need to run this as root or chown your blocks directory to make it work, though.
Perfect! That's exactly what I was looking for, I knew you guys were holding out on me
Tip you guys come CON for the help?
