<p>Although I think it's too early to tell for sure, it appears that I now have a good deal more informative reading that I've found <a href="https://bitcoin.org/en/developer-examples" rel="nofollow">here</a>. I suspect that these documents will eventually help me understand the correct answers to all my questions above. I hadn't realized that my questions were essentially developer questions before now.</p>

<p>I'd still enjoy seeing more user-oriented documentation that would help me understand my questions, so if anyone has any thoughts to share, I'd still welcome them. I do not by any means consider this to be a definitive answer to my several questions above.</p>

<p>UPDATE:</p>

<p>These words (though currently not quite complete as they do not mention bitcoin-cli): "There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin” [or bitcoin-qt]), and a 'headless' version (called bitcoind). They are <strong>completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin [aka bitcoin-qt] or bitcoind on your system at a time</strong> (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit)." from <a href="https://en.bitcoin.it/wiki/Running_Bitcoin" rel="nofollow">this page</a> were also <strong>extremely</strong> helpful to me. They helped me see that to get started, I don't even need to worry about the settings in the bitcoin.conf config file. I can install both bitcoin-qt and bitcoind, start up with bitcoin-qt initially, and then shut it down later in favor of bitcoind.</p>

<p>So for Arch Linux at least, I now think it's best to install all three packages:</p>

<ol>
<li>bitcoind</li>
<li>bitcoin-cli</li>
<li>bitcoin-qt</li>
</ol>

<p>And these are all part of the upstream software called Bitcoin Core used for <strong>complete transparency</strong> and a wallet stored locally (arguably the best security) on <strong>my computer</strong> rather than on someone else's computer.</p>

<p>But one <strong>really valuable</strong> tip I just discovered a few minutes ago is that there's a fairly recent copy of the (21 GB) entire block chain available as a <a href="https://en.bitcoin.it/wiki/Data_directory#Bootstrapping_the_blockchain_from_a_snapshot_distributed_through_BitTorrent" rel="nofollow">torrent file</a>. And in light of that discovery, it's clear to me that to get started as quickly as possible with a local wallet, I should completely download this torrent of the block chain first. And then and <strong>only THEN</strong> should I fire up bitcoind or bitcoin-qt to have that 21GB block chain validated or verified or whatever the correct term is for that. This saves me download time and it saves the Bitcoin network bandwidth from direct downloads via bitcoind or bitcoin-qt.</p>

<p>UPDATE2:</p>

<p>I wrote a detailed procedure for this in the Arch Linux <a href="https://wiki.archlinux.org/index.php/Bitcoin#Installation" rel="nofollow">Bitcoin wiki page</a> that I've reproduced below to improve this answer.</p>

<ol>
<li><p>Verify at least 80GB (22GB * 3 copies + 14GB worth of additional blocks via bitcoind/bitcoin-qt) of free disk space is available</p></li>
<li><p>Install gnupg, deluge, bitcoin-qt, bitcoin-daemon, and bitcoin-cli from the official repositories</p></li>
<li><p>Using a browser, download README.txt, bootstrap.dat.torrent, bootstrap.dat.torrent.gpg, and bootstrap.txt</p></li>
<li><p>Using gnupg, verify the downloaded files as having good signatures (you'll need to first import the signer's public key ID A2DB9CCA)</p></li>
<li><p>Using deluge, download the 22GB bootstrap.dat (perhaps hours depending on your download data rate)</p></li>
<li><p>When bootstrap.dat download is complete:</p>

<ul>
<li><p>leave deluge running until seeding is complete (optional but it helps the community; may require hours or days depending on your upload data rate)</p></li>
<li><p>copy (don't move or you'll interrupt seeding) bootstrap.dat to ~/.bitcoin (don't use a symbolic link as this file will get renamed by bitcoin-qt after it is fully imported, and that too will interrupt seeding)</p></li>
</ul></li>
<li><p>start bitcoind for background import or bitcoin-qt for import with feedback on progress</p></li>
<li><p>bitcoin-qt begins importing the block chain from bootstrap.dat, giving visual and text feedback as to import progress ("Importing from disk..." and eg. "4 years and 24 weeks behind", etc.; this import from disk may require more than one hour)</p></li>
<li><p>the import process duplicates the 22GB bootstrap.dat file into ~/.bitcoin/blocks/, thus roughly doubling the size of ~/.bitcoin from 22GB before starting Bitcoin Core to 44GB after import is complete.</p></li>
<li><p>After import from disk is complete</p>

<ul>
<li><p>bitcoin-qt will show "Synchronizing with network..." and eg. "22 weeks behind..." (a wired network connection here will speed this part of the process but several hours to complete synchronization with network is typical)</p></li>
<li><p>the bootstrap.dat file gets renamed to bootstrap.dat.old</p></li>
<li><p>it should now be safe to remove bootstrap.dat.old from ~/.bitcoin, but a cautious approach would be to wait until your locally stored block chain is fully synchronized with the network</p></li>
</ul></li>
<li><p>quit bitcoin-qt</p></li>
<li><p>then remove ~/.bitcoin/bootstrap.dat.old</p></li>
<li><p>After bitcoin-qt indicates that the local copy of the block chain is fully synchronized with the network (~/.bitcoin/blocks filled 34GB in Feb 02015, then consider quitting bitcoin-qt and do either one of the following:</p>

<ul>
<li><p>start bitcoind to keep the block chain synchronized; feedback as to block chain status can then be had using bitcoin-cli without the additional memory required of bitcoin-qt.</p></li>
<li><p>restart bitcoin-qt running as a minimized window ($ bitcoin-qt -min). Note however that some people have found this commandline argument does not work as advertised.</p></li>
</ul></li>
<li><p>Consider making a backup of your wallet.dat file using bitcoin-qt.</p></li>
<li><p>See the official Bitcoin wiki for additional guidance.</p></li>
</ol>

CC BY-SA 3.0
2015-02-20T09:45:21.703Z
2015-02-23T19:24:36.697Z
2015-02-23T19:24:36.697Z
Kevin Ford The Submariner
<p>Ok, well I've been watching the Bitcoin trend with some interest for several years. And I've finally decided to get involved myself. So yesterday and today I've been reading for several hours from the many resources in <a href="https://bitcoin.stackexchange.com/q/22796/3005">this question</a> and <a href="https://bitcoin.stackexchange.com/a/22840/3005">this great answer</a>. I read <a href="http://evoorhees.blogspot.com/2012/04/bitcoin-libertarian-introduction.html" rel="noreferrer">this blog post</a> in its entirety and think I understood it completely. I understand that in order to pay someone or be paid in BTC, I need a bitcoin ID and that this goes hand-in-hand with getting a BTC "wallet". I understand that there are essentially two distinct options for my BTC wallet:</p>

<ol>
<li>a locally-stored (on my computer) copy of the entire block chain</li>
<li>a remotely-stored (on someone else's computer) copy of the entire
    block chain that is encrypted with credentials such that only I have
    access to it (although Mt. Gox failure and so many others seem to
    show that this is less secure than the former)</li>
</ol>

<p>I think a synonym for option 1 above is "cold-storage" although I'm not certain of that.</p>

<p>I realize that mining for BTC is a different thing altogether that is really only worthwhile with an ASIC or similar hardware, so I'm not at all interested in mining at this point. I just want to get myself an ID and wallet and understand Bitcoin well enough to be able to keep my own copy of the block chain on my local machine and keep it up-to-date. Maybe eventually I'll look into mining, but I'm not interested right now.</p>

<p>From Erik Voorhees blog post, I think I understand that if I want option 1 above (which I do as it seems more secure to me, and convenience is not at all important to me), then I need to install either bitcoind or bitcoin-qt. (I suppose that both of these are considered to be part of "Bitcoin Core" below?) This is reinforced by my review of the software tools I see at bitcoin.org:</p>

<ol>
<li><p><a href="https://bitcoin.org/en/choose-your-wallet#" rel="noreferrer">Bitcoin Core</a>:</p>

<ul>
<li>Control over your money</li>
<li>Full validation</li>
<li><strong>Complete transparency</strong></li>
<li>Vulnerable environment</li>
<li>Improved privacy</li>
</ul></li>
</ol>

<p>whereas the best that any of the others for Linux there:</p>

<ol start="2">
<li><a href="https://bitcoin.org/en/choose-your-wallet#" rel="noreferrer">Electrum</a></li>
<li><a href="https://bitcoin.org/en/choose-your-wallet#" rel="noreferrer">mSIGNA</a></li>
<li><a href="https://bitcoin.org/en/choose-your-wallet#" rel="noreferrer">MultiBit</a></li>
<li><a href="https://bitcoin.org/en/choose-your-wallet#" rel="noreferrer">Armory</a></li>
<li><a href="https://bitcoin.org/en/choose-your-wallet#" rel="noreferrer">Green Address</a></li>
</ol>

<p>can offer regarding transparency is "Basic Transparency".</p>

<p>I understand from <a href="https://bitcoin.stackexchange.com/a/13369/3005">this answer</a> that although it's possible to have them both installed on the same system, one cannot have both bitcoind <strong>and</strong> bitcoin-qt running on the same system at the same time. So my question is about how to configure and get started running bitcoind in Arch Linux; but there are several specific issues I feel like I need to understand better.</p>

<ol>
<li><p>Using bitcoind, at exactly what point will I be generating my ID? I guess it would have to be after I've completed downloading the entire block chain?</p></li>
<li><p>bitcoind.conf wants me to insert an in-the-clear, plaintext, unencrypted username and password into it that I guess bitcoind will read on startup. Exactly what will those credentials be used for by bitcoind? I know the options are named pretty transparently (rpcuser and rpcpassword) and the man page explains that they are  for JSON-RPC connections. But I have only one binary in my Arch bitcoin-daemon package (/usr/bin/bitcoind), so what client is connecting to my running instance of bitcoind using JSON-RPC connections?</p></li>
<li><p>Using bitcoind, at exactly what point will the software begin downloading a copy of the entire block chain? I know that's a big file and may take hours or days to complete.</p></li>
<li><p>If I want to interact with my locally-stored block chain after it is downloaded, then it seems that I must include at least one uncommented line in ~/.bitcoin/bitcoin.conf:</p>

<pre><code>server=1
</code></pre></li>
<li><p>...but what will the simplest bitcoin.conf file that I need look like? For example, will I need to uncomment settings for any of these:</p>

<pre><code>addnode=
connect=
maxconnections=
rpctimeout=
rpcssl=
rpcsslciphers=
rpcsslcertificatechainfile=
rpcsslprivatekeyfile=
keypool=
paytxfee=
min=
minimizetotray=
</code></pre></li>
<li><p>What are other people using for paytxfee, and aside from what bitcoin.conf says, ("Transactions with fees are more likely than free transactions to be included in generated blocks, so may be validated sooner."), why would I set this value to something other than 0.00 (and what is that number anyway? a percentage? so if I set it to 1.00 that is 1.00%)?</p></li>
</ol>

<p>My main problem in understanding now is just connecting the specific settings in bitcoin.conf to my abstract understanding of how the Bitcoin network functions. I think I have a general understanding of the latter, but how to implement the specific concepts of the latter using the settings of the former is not at all obvious to me and after many hours of study, I don't see a clear explanation of it anywhere.</p>

<p>So I'm hoping someone here can shed some light on these issues. After all the questions I've seen on this site, I'm sure I can't be the only one wondering these things.</p>

<p>I considered breaking up this post into 5 or so separate posts and I hope the community will pardon my deciding not to do that. I see all of the several questions above as essentially pieces of the subject question: "How to configure bitcoind in Arch Linux". That's why I left it as one long post. Again, I beg the pardon of the community if that is regarded as a regrettable decision.</p>

CC BY-SA 3.0
2015-02-20T08:46:38.587Z
Still reading other questions after posting, I ran across [this one](http://bitcoin.stackexchange.com/a/16560/3005). But when I do that, I see the following: "Error: There is no RPC client functionality in bitcoind anymore. Use the bitcoin-cli utility instead." But I have no bitcoin-cli binary from my having installed the bitcoin-daemon package in Arch.
Kevin Ford The Submariner
CC BY-SA 3.0
2015-02-20T08:54:46.370Z
The maintainer of the Arch Bitcoin packages, Timothy Redaelli, appears to have split what you need across `bitcoin-daemon` and `bitcoin-cli`, and I can't figure out why.
Nick ODell
CC BY-SA 3.0
2015-02-20T08:57:52.933Z
And, honestly, it would have been better to split this into multiple questions. As it is, I'm not really sure where to start.
Nick ODell
CC BY-SA 3.0
2015-02-20T09:32:28.493Z
After reading [this](https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs), it appears to be the case that this split is present upstream.
Kevin Ford The Submariner
CC BY-SA 3.0
2015-02-20T14:58:18.670Z
Also, it isn't necessary to list all of the things you do understand when asking a question about something you don't understand. Try to be as brief as possible and as detailed as necessary.
morsecoder
CC BY-SA 3.0
2015-02-21T02:09:19.093Z
@NickODell in addition to the official [upstream page](https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs) I referred to above, I just wanted to point out an [answer](http://bitcoin.stackexchange.com/a/13369/3005) on this SE site that also shows your comment above (about Timothy Redaelli having split Bitcoin Core into bitcoin-daemon and bitcoin-cli packages) to be misleading. I didn't realize before today that bitcoind could previously (before v0.9) be run as either server or client, but since v0.10, bitcoind is the RPC server only, and bitcoin-cli is the RPC client only.
Kevin Ford The Submariner
CC BY-SA 3.0
2015-02-21T06:12:45.133Z
@02019 upstream split them into different binaries, sure. But to my knowledge, they never recommended that package creators package them separately. If the answer you linked shows my comment to be misleading, I'm afraid I don't understand how.
Nick ODell
<bitcoind><linux>
How to configure bitcoind in Arch Linux
Kevin Ford The Submariner
# How to configure bitcoind in Arch Linux

(Asked by: username_0 on 2015-02-20)

Ok, well I've been watching the Bitcoin trend with some interest for several years. And I've finally decided to get involved myself. So yesterday and today I've been reading for several hours from the many resources in [this question](https://bitcoin.stackexchange.com/q/22796/3005) and [this great answer](https://bitcoin.stackexchange.com/a/22840/3005). I read [this blog post](http://evoorhees.blogspot.com/2012/04/bitcoin-libertarian-introduction.html) in its entirety and think I understood it completely. I understand that in order to pay someone or be paid in BTC, I need a bitcoin ID and that this goes hand-in-hand with getting a BTC "wallet". I understand that there are essentially two distinct options for my BTC wallet:

1. a locally-stored (on my computer) copy of the entire block chain
2. a remotely-stored (on someone else's computer) copy of the entire
   block chain that is encrypted with credentials such that only I have
   access to it (although Mt. Gox failure and so many others seem to
   show that this is less secure than the former)

I think a synonym for option 1 above is "cold-storage" although I'm not certain of that.

I realize that mining for BTC is a different thing altogether that is really only worthwhile with an ASIC or similar hardware, so I'm not at all interested in mining at this point. I just want to get myself an ID and wallet and understand Bitcoin well enough to be able to keep my own copy of the block chain on my local machine and keep it up-to-date. Maybe eventually I'll look into mining, but I'm not interested right now.

From Erik Voorhees blog post, I think I understand that if I want option 1 above (which I do as it seems more secure to me, and convenience is not at all important to me), then I need to install either bitcoind or bitcoin-qt. (I suppose that both of these are considered to be part of "Bitcoin Core" below?) This is reinforced by my review of the software tools I see at bitcoin.org:

1. [Bitcoin Core](https://bitcoin.org/en/choose-your-wallet#):

   * Control over your money
   * Full validation
   * **Complete transparency**
   * Vulnerable environment
   * Improved privacy

whereas the best that any of the others for Linux there:

2. [Electrum](https://bitcoin.org/en/choose-your-wallet#)
3. [mSIGNA](https://bitcoin.org/en/choose-your-wallet#)
4. [MultiBit](https://bitcoin.org/en/choose-your-wallet#)
5. [Armory](https://bitcoin.org/en/choose-your-wallet#)
6. [Green Address](https://bitcoin.org/en/choose-your-wallet#)

can offer regarding transparency is "Basic Transparency".

I understand from [this answer](https://bitcoin.stackexchange.com/a/13369/3005) that although it's possible to have them both installed on the same system, one cannot have both bitcoind **and** bitcoin-qt running on the same system at the same time. So my question is about how to configure and get started running bitcoind in Arch Linux; but there are several specific issues I feel like I need to understand better.

1. Using bitcoind, at exactly what point will I be generating my ID? I guess it would have to be after I've completed downloading the entire block chain?
2. bitcoind.conf wants me to insert an in-the-clear, plaintext, unencrypted username and password into it that I guess bitcoind will read on startup. Exactly what will those credentials be used for by bitcoind? I know the options are named pretty transparently (rpcuser and rpcpassword) and the man page explains that they are for JSON-RPC connections. But I have only one binary in my Arch bitcoin-daemon package (/usr/bin/bitcoind), so what client is connecting to my running instance of bitcoind using JSON-RPC connections?
3. Using bitcoind, at exactly what point will the software begin downloading a copy of the entire block chain? I know that's a big file and may take hours or days to complete.
4. If I want to interact with my locally-stored block chain after it is downloaded, then it seems that I must include at least one uncommented line in ~/.bitcoin/bitcoin.conf:

   ```
   server=1

   ```
5. ...but what will the simplest bitcoin.conf file that I need look like? For example, will I need to uncomment settings for any of these:

   ```
   addnode=
   connect=
   maxconnections=
   rpctimeout=
   rpcssl=
   rpcsslciphers=
   rpcsslcertificatechainfile=
   rpcsslprivatekeyfile=
   keypool=
   paytxfee=
   min=
   minimizetotray=

   ```
6. What are other people using for paytxfee, and aside from what bitcoin.conf says, ("Transactions with fees are more likely than free transactions to be included in generated blocks, so may be validated sooner."), why would I set this value to something other than 0.00 (and what is that number anyway? a percentage? so if I set it to 1.00 that is 1.00%)?

My main problem in understanding now is just connecting the specific settings in bitcoin.conf to my abstract understanding of how the Bitcoin network functions. I think I have a general understanding of the latter, but how to implement the specific concepts of the latter using the settings of the former is not at all obvious to me and after many hours of study, I don't see a clear explanation of it anywhere.

So I'm hoping someone here can shed some light on these issues. After all the questions I've seen on this site, I'm sure I can't be the only one wondering these things.

I considered breaking up this post into 5 or so separate posts and I hope the community will pardon my deciding not to do that. I see all of the several questions above as essentially pieces of the subject question: "How to configure bitcoind in Arch Linux". That's why I left it as one long post. Again, I beg the pardon of the community if that is regarded as a regrettable decision.

**Tags:** bitcoind, linux

> **Comments:**
> **username_0**: Still reading other questions after posting, I ran across [this one](http://bitcoin.stackexchange.com/a/16560/3005). But when I do that, I see the following: "Error: There is no RPC client functionality in bitcoind anymore. Use the bitcoin-cli utility instead." But I have no bitcoin-cli binary from my having installed the bitcoin-daemon package in Arch.  
> **username_1**: The maintainer of the Arch Bitcoin packages, Timothy Redaelli, appears to have split what you need across `bitcoin-daemon` and `bitcoin-cli`, and I can't figure out why.  
> **username_1**: And, honestly, it would have been better to split this into multiple questions. As it is, I'm not really sure where to start.  
> **username_0**: After reading [this](https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs), it appears to be the case that this split is present upstream.  
> **username_2**: Also, it isn't necessary to list all of the things you do understand when asking a question about something you don't understand. Try to be as brief as possible and as detailed as necessary.  
> **username_0**: @username_1 in addition to the official [upstream page](https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs) I referred to above, I just wanted to point out an [answer](http://bitcoin.stackexchange.com/a/13369/3005) on this SE site that also shows your comment above (about Timothy Redaelli having split Bitcoin Core into bitcoin-daemon and bitcoin-cli packages) to be misleading. I didn't realize before today that bitcoind could previously (before v0.9) be run as either server or client, but since v0.10, bitcoind is the RPC server only, and bitcoin-cli is the RPC client only.  
> **username_1**: @02019 upstream split them into different binaries, sure. But to my knowledge, they never recommended that package creators package them separately. If the answer you linked shows my comment to be misleading, I'm afraid I don't understand how.  

---

## 1 answers

### Answer by username_0 on 2015-02-20. Score: 2

Although I think it's too early to tell for sure, it appears that I now have a good deal more informative reading that I've found [here](https://bitcoin.org/en/developer-examples). I suspect that these documents will eventually help me understand the correct answers to all my questions above. I hadn't realized that my questions were essentially developer questions before now.

I'd still enjoy seeing more user-oriented documentation that would help me understand my questions, so if anyone has any thoughts to share, I'd still welcome them. I do not by any means consider this to be a definitive answer to my several questions above.

UPDATE:

These words (though currently not quite complete as they do not mention bitcoin-cli): "There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin” [or bitcoin-qt]), and a 'headless' version (called bitcoind). They are **completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin [aka bitcoin-qt] or bitcoind on your system at a time** (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit)." from [this page](https://en.bitcoin.it/wiki/Running_Bitcoin) were also **extremely** helpful to me. They helped me see that to get started, I don't even need to worry about the settings in the bitcoin.conf config file. I can install both bitcoin-qt and bitcoind, start up with bitcoin-qt initially, and then shut it down later in favor of bitcoind.

So for Arch Linux at least, I now think it's best to install all three packages:

1. bitcoind
2. bitcoin-cli
3. bitcoin-qt

And these are all part of the upstream software called Bitcoin Core used for **complete transparency** and a wallet stored locally (arguably the best security) on **my computer** rather than on someone else's computer.

But one **really valuable** tip I just discovered a few minutes ago is that there's a fairly recent copy of the (21 GB) entire block chain available as a [torrent file](https://en.bitcoin.it/wiki/Data_directory#Bootstrapping_the_blockchain_from_a_snapshot_distributed_through_BitTorrent). And in light of that discovery, it's clear to me that to get started as quickly as possible with a local wallet, I should completely download this torrent of the block chain first. And then and **only THEN** should I fire up bitcoind or bitcoin-qt to have that 21GB block chain validated or verified or whatever the correct term is for that. This saves me download time and it saves the Bitcoin network bandwidth from direct downloads via bitcoind or bitcoin-qt.

UPDATE2:

I wrote a detailed procedure for this in the Arch Linux [Bitcoin wiki page](https://wiki.archlinux.org/index.php/Bitcoin#Installation) that I've reproduced below to improve this answer.

1. Verify at least 80GB (22GB \* 3 copies + 14GB worth of additional blocks via bitcoind/bitcoin-qt) of free disk space is available
2. Install gnupg, deluge, bitcoin-qt, bitcoin-daemon, and bitcoin-cli from the official repositories
3. Using a browser, download README.txt, bootstrap.dat.torrent, bootstrap.dat.torrent.gpg, and bootstrap.txt
4. Using gnupg, verify the downloaded files as having good signatures (you'll need to first import the signer's public key ID A2DB9CCA)
5. Using deluge, download the 22GB bootstrap.dat (perhaps hours depending on your download data rate)
6. When bootstrap.dat download is complete:

   * leave deluge running until seeding is complete (optional but it helps the community; may require hours or days depending on your upload data rate)
   * copy (don't move or you'll interrupt seeding) bootstrap.dat to ~/.bitcoin (don't use a symbolic link as this file will get renamed by bitcoin-qt after it is fully imported, and that too will interrupt seeding)
7. start bitcoind for background import or bitcoin-qt for import with feedback on progress
8. bitcoin-qt begins importing the block chain from bootstrap.dat, giving visual and text feedback as to import progress ("Importing from disk..." and eg. "4 years and 24 weeks behind", etc.; this import from disk may require more than one hour)
9. the import process duplicates the 22GB bootstrap.dat file into ~/.bitcoin/blocks/, thus roughly doubling the size of ~/.bitcoin from 22GB before starting Bitcoin Core to 44GB after import is complete.
10. After import from disk is complete

    * bitcoin-qt will show "Synchronizing with network..." and eg. "22 weeks behind..." (a wired network connection here will speed this part of the process but several hours to complete synchronization with network is typical)
    * the bootstrap.dat file gets renamed to bootstrap.dat.old
    * it should now be safe to remove bootstrap.dat.old from ~/.bitcoin, but a cautious approach would be to wait until your locally stored block chain is fully synchronized with the network
11. quit bitcoin-qt
12. then remove ~/.bitcoin/bootstrap.dat.old
13. After bitcoin-qt indicates that the local copy of the block chain is fully synchronized with the network (~/.bitcoin/blocks filled 34GB in Feb 02015, then consider quitting bitcoin-qt and do either one of the following:

    * start bitcoind to keep the block chain synchronized; feedback as to block chain status can then be had using bitcoin-cli without the additional memory required of bitcoin-qt.
    * restart bitcoin-qt running as a minimized window ($ bitcoin-qt -min). Note however that some people have found this commandline argument does not work as advertised.
14. Consider making a backup of your wallet.dat file using bitcoin-qt.
15. See the official Bitcoin wiki for additional guidance.


---

