search

PulpCattel / Tails-BitcoinCore-Wasabi

Straightforward tutorial on how to create a Tails setup to manage your lovely sats.
17 stars 0 forks source link

Attached an example of a bitcoin.conf #2

Open ghost opened 3 years ago

ghost commented 3 years ago

Hi mate, Have created a bitcoin.conf that will work very well on this setup.

proxy=127.0.0.1:9050 listen=1 bind=127.0.0.1 onlynet=onion dnsseed=0 dns=0 dbcache=4500

Row 7; dbcache=4500 will force Bitcoin to run on 4,5 Gb ram instead of the 450 Mb that is standard. If the computer has 8 Gb ram this is a good option. If more ram than this number can be increased to speed up the calculation of the blocks and thereby download them faster. Its never really the CPU that reduces the speed of downloading the blockchain. Its nearly always the working memory.

Cheers

PulpCattel commented 3 years ago

Hey, thanks.

Please edit your message and write here your bitcoin.conf, no need for an extra file nor to require viewers to download stuff.

In general, Bitcoin Core configuration are out of scope of this guide. Apart from prune= and proxy=, which are almost always necessary for Tails, the only other mention is to onlynet= and dns=, which one may argue for being already out of scope. If someone wants to customize his bitcoin.conf, there are plenty of resources about it, including the official documentation (thinking about it, I could add a link to it).

Anyhow, if you edit your message I'll keep this issue open for others to see.

ghost commented 3 years ago

Hi mate, I attached the file just to make it easier if you wanted to use it as an example. I don't require anybody to download anything. The good thing with GitHub is that every file can be open and inspected easily.

I agree with you on setup of the bitcoin.conf. However prune disables importprivkey and for me going from a cold storage a full Bitcoin Core node is therefore required. Now 12 years since the blockchain started using dbcache=450 (standard) makes the full download way to slow. Just adding a zero and the speed picks up greatly.

Cheers

PulpCattel commented 3 years ago

I think listen=1 and bind=127.0.0.1 are superfluous?

I have not tested it, but I'm pretty sure importprivkey works with pruned too. I guess you have to pass false as rescan argument (it's true by default and pruned nodes cannot do rescan). Also note that if you have disabled private keys at wallet creation, that wallet won't be able to have any private key; so if this is the case you'll have to create a new non watch-only wallet.

Absolutely, dbcache is very convenient during IBD.

ghost commented 3 years ago

Sorry, didn't mean to close the subject. My mistake. Sorry about that.

You made some good and valid points. I will consider them. Thanks