pull down to refresh

0 sats \ 3 replies \ @moptosh 3h \ parent \ on: Peter Wuille post about dropping OP_RETURN limit bitcoin
I'm trying to understand. If I don't update my Bitcoin Core node to v30 and stick with previous versions, there won't be any adoption if everyone else does the same. Conversely, if everyone updates to v30, the only alternative I see is switching to Bitcoin Knots. But the big issue is that Knots is a fork, and only 22% of nodes in operation use it.so what should we do
write
preview
0 sats \ 2 replies \ @DarthCoin OP 3h
Whatever you will do is the same. Announcing you are running x or y node is just virtue signaling. All those RPis nodes on umbrel or start9 if they are not real full nodes with open ports and big mempools then are just personal nodes that really do not help in any way the network. Virtue signaling means 0 impact.
reply
0 sats \ 1 reply \ @moptosh 2h
So, to summarize: Running a "bitcoin-d" node exposed on port 8333 behind a VPN that allows port forwarding to maintain anonymity.
reply
0 sats \ 0 replies \ @DarthCoin OP 2h
https://bitnodes.io/what-is-a-bitcoin-node/#reachable-vs-unreachable-nodes so yeah a TLDR:
  • port 8333 open
  • bitcoin.conf configured properly for more inbound connections and mempool size if you really want to be a seeder.
maxuploadtarget=<MiB per day>
listen=1
maxconnections=<num>
minrelaytxfee=
maxmempool=2000
mempoolexpiry=672
Otherwise is just useless virtue signaling or personal nodes, not full nodes.
reply