Congratulation, Bitcoin has reached 500 GB size hard disk data

[franky1]

if you dont want to be a full node thats fine.. but understand it from the prospective of those that DO

people who want to be a full node.. actually want to be a full node

And people who want to prune it, want a pruned node. You're missing the point: let them choose!

if everyone pruned... no one would have full blockchain data from genesis to now anymore.

Don't worry, I have a backup And I'm pretty sure you have one too, and so do thousands of other Bitcoin users.

= centralisation.

One of the beautiful things of decentarlisation is having the freedom to choose.

Unacceptable.  People can only use Bitcoin in a manner that franky1 approves.  

(but we're still not allowed to call him a fascist)

THIS TOPIC is about the full archiving of bitcoin.
where people want to discuss archiving the full blockchain

yes people can and do have a choice but they should be informed about it, informed about the choice, informed of the differences..
.. something loyce and doomad fail to do. they pretend pruning is the same as being a full node, when its not

[1715209287]

1715209287

[1715209287]

1715209287

[Sarah Azhari]

I really don’t like upgrading, verifying my download always concerns me.

why would that concern you? are you worried that the blockchain is invalid or something?

Maybe he is one of the perfect person. Same as me, sometimes I'm too lazy to verify my download because many steps we must go through gradually like Download the list of cryptographic checksums, Downloading the signatures to validity, and many other steps (11 steps ) which we must follow or It could be complicated if never used before.

[LoyceV]

Downloading the signatures to validity, and many other steps (11 steps ) which we must follow or It could be complicated if never used before.

That's something they can improve: Tails for instance has a "Select your download..."-button, and verifies the file within the browser. I'm not sure how useful that is when the server gets compromised, but doesn't the same apply to Bitcoin Core's SHA256SUMS?

[YUriy1991]

Is the default hard disk still good to use, or move to SSD?

I just try to download, but when over 3 days, my hard disk is slow to receive blockchain data, seems low in header sync when opening and closing bitcoin core. (I use a default Hard disk of 10 terabyte)

In my opinion In terms of storage, while a hard disk may work, using an SSD would significantly increase the speed and efficiency of downloading and storing the blockchain data. If your current 10 terabyte hard disk is slow, you may consider upgrading to an SSD or increasing your internet speed for faster syncing.

[BlackHatCoiner]

That's something they can improve: Tails for instance has a "Select your download..."-button, and verifies the file within the browser.

I don't think the button is to verify the authenticity of the software. If you notice, it says "make sure that it is safe and was not corrupted". It's possible that your Internet connection is unstable and gets interrupted, which if I remember correctly can result in file corruption in modern browsers.

The real question is why not save a step and verify the OpenPGP signature beforehand? It will prompt invalid if file is corrupted.

[franky1]

Downloading the signatures to validity, and many other steps (11 steps ) which we must follow or It could be complicated if never used before.

the other thing is.
if your downloading core from that one site.. but also downloading the signatures AND keys from that one site. then you are already failing. because IF that one site was compromised then all info on that one site is compromised. so obviously the keys would match the file because the corrupter/malicious hacker tailered all info available on the site to match his edited node download file

its better to get the node software from a trusted source(the site) and TEST that trust by looking for the signatures from the devs own servers/websites (decentralised sources) to make sure it all matches

OR save all that time by just grabbing the code from github and using a compiler that way you know what has been put into your node