Is a pruned node helpful for the Bitcoin community?

A bitcoin node have two foremost sorts of interactions with different nodes:

• sending confirmed blocks, saved on blocks folder: to do it, specifically in nodes syncing from scratch, the bitcoin should have all blocks saved on disk, pruned nodes doesn’t have all blocks, so that they might not be used for syncing from scratch. It may be managed utilizing -prune setting.
• sending transactions, that may be retrieved utilizing information in chainstate folder: the chainstate are the worldwide state of blockchain that now have round 13GB, it can’t be pruned and should be loaded within the RAM to confirm transactions, retrieve and propagate them. Might be partially managed utilizing -blocksonly setting.

These settings rely on the best way you wish to assist the bitcoin community:
If you wish to serve nodes that do Preliminary block obtain or syncing from some days, you shouldn’t prune your node and you need to use -blocksonly setting, that can cut back load and bandwidth, by not propagating transactions, solely blocks. We will name this node a “archive node”.

If you wish to propagate transactions, newest 288 blocks, or use your node for mining, you shouldn’t use -blocksonly however you possibly can set -prune to cut back the area of storing some historic blocks.

In my assessments i used a non-pruned full node. The node transferred round 400GB/Month, but it surely was linked to three ISPs, Tor and I2P. I used bitcoin-cli getnettotals to test.

It doesn’t should be on port 8333, and it’ll not matter if the port are closed for inbound connections, the node will get much less connections and won’t be proven in bitnodes.io
I additionally haven’t any public port in IPv4, however i do have in IPv6, you possibly can test in case your IPv6 are firewalled or not.
You should use Tor and I2P to have a public handle too.
Its attainable to have a public handle utilizing a VPS (or one other machine) that does have a public handle, on this case you want a reverse tunnel to that machine, it may be made utilizing SSH -R choice. On this case you add -externalip=IP choice to the general public IP of the server, it will likely be used just for inbound connections, since its not routable for outbound (npr).