25 sats \ 2 replies \ @DarthCoin 12 Nov 2023 \ on: Rant: the blocksize war propaganda has lead to myths bitcoin
I agree with your rant.
Don't forget to say that most of these clueless "node runners" where bombarded with videos and podcasts and marketing shills for all those RPi "nodes" from the 2020-2021 era selling them these "machines" as being the ultimate node machines.
In the end was all about selling hardware and make a buck.
You will never see from these hardware sellers and so called "node software" promoters that in order to run a fully public node that really help the network you would need to do some configurations and have some SPECIFIC hardware and connection.
- port 8333 open and configured specified number of outbound connections allowed. This will imply to have a good RAM machine and a good internet connection, in order to be able to share the seeding blocks to other many nodes. A RPi will just die if you open that outbound to unlimited connections.
- a good size of local mempool configured. The default 300MB size of the mempool sometimes is not enough. A 2GB mempool on a RPi node is just killing it, instantly.
- bitcoin.conf must be configured with maxuploadtarget and maxconnections in order to "help the network". Otherwise is worthless, just a personal node that doesn't count.
As I explained more aspects here:
https://darthcoin.substack.com/p/lightning-node-maintenance
The default 300MB size of the mempool sometimes is not enough.
It's plenty enough, and it's quite rare to have a good reason to change it. The main purpose of the mempool is simply to help transactions be propagated for the purpose of being mined, by storing what transactions have already been propagated. Transactions with low fees aren't going to be mined soon, if ever, so there aren't good reasons to propagate them or store them in mempools. Propagating them is generally just a waste of your peers' bandwidth.
bitcoin.conf must be configured with maxuploadtarget and maxconnections in order to "help the network". Otherwise is worthless, just a personal node that doesn't count.
Huh? The defaults for both those options work fine for the vast majority of people. If anything, we're better off if a large number of people run a lot of smaller nodes. That makes deanonymizing Bitcoin transactions by tracing them to their origins much harder than a small number of big nodes.
port 8333 open and configured specified number of outbound connections allowed.
Having nodes that aren't publicly accessible improves privacy for everyone by making it harder to identify peering connections, again making it harder to trace transactions back to their source.
reply
agreed
reply