{Bitcoin} Stack Exchange is a question and answer site for {Bitcoin} crypto-currency enthusiasts. It only takes a minute to sign up.
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
Asked
Viewed
5 times
We are working on a {Bitcoin} project for which we need to have the {bitcoin} node. The point is that we do not need to have the entire {bitcoin} node downloaded but only from the moment we start the project and therefore we opt for pruned node. The current setting is pruned = 1
, because we don’t need to prune the old blocks every X size of blockes.
So, after starting the node with pruned configuration, we see that old blocks are still being downloaded because in a matter of 20 minutes we had more than 10 gigabytes used space.
We have a wrong idea about “pruned node” or we have something wrong or partially configured?
SamYan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
So, after starting the node with pruned configuration, we see that old blocks are still being downloaded because in a matter of 20 minutes we had more than 10 gigabytes used space.
Pruning does not mean not downloading; it means deleting them after they’ve been downloaded and verified.
{Bitcoin} Core always downloads and validates the entire history (for now).
2