I am thinking about installing a node on a Raspberry PI. What are the advantages and disadvantages of a pruned node? Do you have experience with a pruned node?
Thanks in advance.
I would not start with this question. The important question is: what do you want to do with that node, what do you want to achieve with running a node? You want only a Bitcoin node or also a LN node?
Then you start looking for solutions. Are plenty.
Even this proposal from fiatjaf #26084
You can even run a node on your mobile, if you want a "small size". Look into Blixt mobile LN node.
reply
Thank you I will have a look.
Honestly, get a full node. HDDs with 1tb are so cheap. If you are techy you can also buy a used laptop on craigslist and screw the hdd out which is probably even cheaper.
reply
Are HDD's not too slow, I hear a lot of people using SSD's because of speed.
tl;dr I'd encourage you to run a full node.
In order to get a pruned node first you have to download the entire blockchain, and then prune it. So you'll need the same disk space, at least initially.
You could sync it in a separate, larger HDD then prune it and move the block data to the smaller disk.
There's also prunednode.today if you trust Stepan but that's generally frowned upon.
Pruned nodes don't have all block data so they can't help new nodes get in sync from block 0. In that sense they're only partially helpful to the network.
And with a pruned node you can't run your own instance of mempool.space because it won't have all the txs.
Remember, HDD is fine it doesn't have to be quick. Let it take a month to sync, who cares.
In summary, pruned nodes:
  • require the same disk capacity
  • can't help new nodes come online
  • have limited usefulness
reply
Correction: Pruned node will in summary download all the blocks, but at one moment it will only use -pruned=N where N is a number of megabytes, at least 550. When it syncs with the latest block, it will have a chainstate with the same idea of the state like any other full node that has all the historical blocks.
Yes, I have experience with both pruned node and a non-pruned node. A pruned node can still act as a full member of the network by verifying all the transactions (and forwarding them to other nodes if they are valid).
One can also mine on a pruned node or run a btc-rpc-explorer against it.
And a pruned node can even help your new nodes come up, as you can simply copy the needed files and start a new node (see https://prunednode.today/).
But yes, very thin ice discussing this topic with others because this topic is (and rightfully so) very opinionated. It touches the basics of what Bitcoin is. If you have the space for it, run a full node with all the historic blocks. If not, run a pruned node which is the second best. And preferable do the initial block download yourself, but if you know what you are doing, feel free to do it otherwise. In the end your node will have the same chainstate and last blocks, no matter what you do. But do it. Learn in practice. You'll feel the difference.
reply
I own both a full node and a pruned one on different machines. I'd say go for the full node, if needed save a bit of extra money for the 1TB SSD, that should keep you running for a few years worth of blocks.
My experience is that the downsides of a pruned node (IE: not being able to check for transactions previous to a certain date) are not worth it. For example, I was offering my friends to connect to my node if they needed to check transactions, but that won't worked on the pruned one. Same for my wallets if somehow I skip the pruned blocks.
reply