pull down to refresh

I have one but it's a candidate to be scrapped when I get to it. I used to have that running for an external indexer to just pick the last blocks off, but I no longer use that and it's in disarray.

I also have 3 full, 2 sync'd (one for serving archive, 1 private one that doesn't allow incoming) and 1 unsync'd (for the rpi4 tests I still need to finish) - those I do use.

I have seen pruned nodes catch some hate, but I have heard of people successfully running lightning nodes on a pruned Bitcoin node (I have not successfully done so, myself).

reply
226 sats \ 2 replies \ @optimism 3h

I think the hate is aimed at the virtue signaling of "I'm running a node" when it's pruned or firewalled or tor-only, because if everyone would do that then there wouldn't be a network.

But there are definite scenarios in which you'll want to run a pruned node - based on personal circumstance. So don't feel hated just because there are haters. If everyone is sovereign then there is free choice, though it would be awful if there is tragedy of the commons on archival node slots. So if you can run a full node, run that.

reply
101 sats \ 1 reply \ @Scoresby OP 2h

I'm surprised that the poll has more than 50% saying they prune (at 23 responses). I didn't think it was that common.

I think that many people just go with defaults, and last time I checked core has a popup on ibd that says do you wanna prune?

reply
103 sats \ 0 replies \ @optimism 2h

I think many home nodes are on old spare hardware, so its not that surprising. But I too answered yes even though I run a fully public full node too. So its maybe a bit skewed.

reply