Hello, newb here wondering about the wisdom of running pruning on my Core 0.12 node. I set prune=10000, which I believe that should store quite a few old transactions. The 61GB blockchain got pruned down quickly to 12GB and the node seems to be running fine.
However I notice that Classic people are mining blocks, and am contemplating what it will mean down the road if blocks need to be rolled back or there is a hard fork. I don't fully understand the technical ramifications of pruning, but my thought is that nodes that are pruned may need to reindex so perhaps this is not the best choice? Thanks for any insights.
Pruning and forks are two completely unrelated things.
With block file pruning, you are only storing some amount of the blockchain. It will always contain the most recent blocks that your node knows about.
Forks are simply new blockchains that stem off of the existing one. With Bitcoin Classic, new blocks are mined which signal forking. When you receive those blocks, the current blocks are still valid so your node accepts them and adds the block to its database and it removes an older block to maintain the number you specified. Forks will not roll anything back and nothing in the blockchain will be rolled back unless there is some major bug and accidental fork that happens like the one that happened in 2013.
