Quote from: Turner77 on July 29, 2017, 10:28:27 PM

Also, the speed of your Internet connection is a big factor. If you have ISP enforced limits on your downloads, or data caps, then that is a factor beyond your control and you will have to live with it (or get a different ISP).

It is actually more CPU bound than network bound... (You'll most likely find your network is hardly being used, while your CPU is being hammered). Crypto hashing when verifying the blocks downloaded is generally the bottleneck, so the speed of your internet connection is largely irrelevant (assuming you're not on dialup Tongue

)...

Quote

If you don't want the ENTIRE Bitcoin blockchain, I've heard that you can also download just part of it with the -prune=nnn command.

When running with pruning switched on, you still have to download the entire blockchain... that is to say, you will still need to download the 130+ gigs to get it "synced". However, it doesn't store all 130+gigs on your disk, so the "available" storage requirements are a lot lower.