What is the quickest way to bring a bitcoind node up handling 99% of edge cases?

What is the quickest way to bring a bitcoind node up handling 99% of edge cases?

Currently when syncing a bitcoind node from scratch the time of going from zero (0) to about 50% is a very fast process but somewhere between 50%-75% it slows down considerably and at 75%-85% it grinds to an almost halt.

Assuming that the blocks that are being verified during that time are what is causing the slowdown I'm wondering if there is a way to basically clone a node by still running and validating a full node but at least trusting the blocks up until some number that is far enough in the past to handle 99% of edge cases.

I know that cloning the disk is possible but transferring that to a new VPS for instance is not so looking for ways to speed up the process for everyone without sacrificing security.

Known Optimizations

Setting the dbcache to a higher value (currently using 2000 on a 4gb RAM machine which is 25% of the available RAM)

https://ift.tt/2SrAO4G

Comments

Post a Comment

Popular posts from this blog

bitcoin node: what is the difference between simnet and regtest?

bitcoin node: what is the difference between simnet and regtest? btcd, and presumably other bitcoin node implementations, seem to have 4 network options: mainnet testnet regtest simnet. I get that mainnet and testnet both are "public" in that your node will communicate with other nodes and that both have an existing blockchain and genesis block. However, from what I can tell, both simenet and regtest both create a local only blockchain, and both will create a new genesis block. I this case, what is the difference, and which is better (easier) for developing bitcoin applications? This is what the documentation has to say: --regtest Use the regression test network --simnet Use the simulation test network https://ift.tt/2TAMkwe
Read more

How to check if Electrum is masking my IP with the Tor proxy?

How to check if Electrum is masking my IP with the Tor proxy? When i start Electrum from the command line i see this mensage: (python3:7069): dbind-WARNING **: 14:09:58.452: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken What does it mean? I just installed Electrum following this tutorial: http://docs.electrum.org/en/latest/tor.html I followed the instructions from this topic " Option 2: Multiple servers but Tor Main ". I installed Electrum using the command line on Ubuntu, check the " Installation from Python sources " on this link https://electrum.org/#download if you want to see the codes. And i used this code bellow to download the Signatue keys: $ gpg --keyserver pool.sks-keyservers.net --recv-keys 2BD5824B7F9470E6 I checked the both checkbox: 1)...
Read more

Need help to recover blpckchain.info wallet, my wife forgot her password and the brute force with btcrecover is not catching the password

Need help to recover blpckchain.info wallet, my wife forgot her password and the brute force with btcrecover is not catching the password I used btcrecover to extract the wallet file (wallet.aes.json) from a blockchain account and I have been running btcrecover with dictionaries of my making but it has been going on for weeks and I am running out of ideas on how to permutate what my wife and I think the password could have been. Is there a way to just manually transfer the btc from the old wallet into a new wallet we do have access to or is there any way to extract the password or private keys directly from the wallet file? We have: the phone with the original wallet app installed, the wallet file pulled using btcrecover, access to the email to allow authorization to access, the wallet identifier that was sent to her email when she first signed up, the phone which has the wallet, the pin that was used for the wallet, and we know how much btc is in the account. We do not have: The pri...
Read more