|
Title: Creating Bootstrap.dat on Ubuntu 14.XX Post by: valkir on March 22, 2015, 11:30:38 PM Hi
I recently did a new setup at home and want to put a nodes on it. I already have a ubuntu with full bitcoin-qt running on it. Could someone provide a nice step by step way to make my own bootstrap.dat so I can transfert it to my new server. Thanks ;D Cheer Valkir Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: grue on March 23, 2015, 12:14:07 AM Creating a bootstrap.dat file not an optimal solution because bitcoind will need to verify the data upon import, which takes a significant amount of time. The best solution would be to stop bitcoind, and copy the entire ~/.bitcoin folder.
but if you insist on using bootstrap.dat, https://github.com/bitcoin/bitcoin/tree/master/contrib/linearize Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: valkir on March 23, 2015, 12:18:01 AM Ok great! So I could only back up all the ./bitcoin folder and erase wallet.dat to start a new nodes.
Right ? Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: grue on March 23, 2015, 12:23:10 AM Yes.
Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: valkir on March 23, 2015, 01:18:18 AM Thanks you grue! ;D
What is or was the purpose of bootstrap.dat ? Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: shorena on March 23, 2015, 08:32:59 AM Thanks you grue! ;D What is or was the purpose of bootstrap.dat ? To speed up the download without having to trust the party providing the data. Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: spin on March 23, 2015, 10:11:19 AM Hi I recently did a new setup at home and want to put a nodes on it. I already have a ubuntu with full bitcoin-qt running on it. Could someone provide a nice step by step way to make my own bootstrap.dat so I can transfert it to my new server. Thanks ;D Cheer Valkir A slower alternative (than copying the files) is to add a connect/addnode in the conf of the new node to point to the existing node. It will then download from your existing node (assuming v0.10). It's easier to set up but the new node will still verify all data again. The advantage is that you can probably leave this config up as you probably don't need to make both nodes available externally. Your new node can just continue to leech of the existing node in future. Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: valkir on March 23, 2015, 01:41:06 PM Thanks you grue! ;D What is or was the purpose of bootstrap.dat ? To speed up the download without having to trust the party providing the data. Thanks ;D Hi I recently did a new setup at home and want to put a nodes on it. I already have a ubuntu with full bitcoin-qt running on it. Could someone provide a nice step by step way to make my own bootstrap.dat so I can transfert it to my new server. Thanks ;D Cheer Valkir A slower alternative (than copying the files) is to add a connect/addnode in the conf of the new node to point to the existing node. It will then download from your existing node (assuming v0.10). It's easier to set up but the new node will still verify all data again. The advantage is that you can probably leave this config up as you probably don't need to make both nodes available externally. Your new node can just continue to leech of the existing node in future. Could I will probably do that. But I will also like to have a backup of the blockchain in case something happen and I need to reboot all my setup. Dont want to downlaod 34gb again. :P Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: icanscript on March 23, 2015, 10:48:33 PM This is what you need,
I have done it many times. Code: https://github.com/bitcoin/bitcoin/tree/master/contrib/linearize Title: Re: Creating Bootstrap.dat on Ubuntu 14.XX Post by: spin on March 24, 2015, 12:23:30 PM A slower alternative (than copying the files) is to add a connect/addnode in the conf of the new node to point to the existing node. It will then download from your existing node (assuming v0.10). It's easier to set up but the new node will still verify all data again. The advantage is that you can probably leave this config up as you probably don't need to make both nodes available externally. Your new node can just continue to leech of the existing node in future. Could I will probably do that. But I will also like to have a backup of the blockchain in case something happen and I need to reboot all my setup. Dont want to downlaod 34gb again. :P |