pull down to refresh
21 sats \ 0 replies \ @BlueSlime 17 Apr 2022
Shout-out to https://prunednode.today
You can launch a new node and get synced to the main chain in less than 30m.
reply
20 sats \ 0 replies \ @G 17 Apr 2022
Well, i guess i know how I'll be spending the rest of my weekend
reply
0 sats \ 0 replies \ @creativowinder 18 Apr 2022
interesting I will try to download and mount the node, we will see if the internet connection allows me
reply
0 sats \ 2 replies \ @cryptocoin 17 Apr 2022
That last part has a link to this:
Running A Full Node - Minimum Requirements
https://bitcoin.org/en/full-node#minimum-requirements
reply
40 sats \ 1 reply \ @DarthCoin 17 Apr 2022
LOL are you joking?
The whole Bitcoin block data is today around 500GB !
Without a 1TB drive don't even think about running a full node.
reply
7 sats \ 0 replies \ @cointastical 17 Apr 2022
The article that this post links to says:
But that 7 GB part right below is from the bitcoin.org website.
I looked at the github source for the site and it gets that from a configuration setting:
{{site.text.bitcoin_datadir_gb_pruned}}
So that is assuming that is in pruned mode. I don't know if 7 GB is still accurate, I suspect it is a bit low now.
But that is misleading, as most aren't looking to run a pruned node.
I've opened an issue on Bitcoin.org repo, Issue #3868 requesting that pruned mode be clarified there. I've also opened Issue #3867 requesting that the values in _config.yaml are updated.
reply