pull down to refresh

0 sats \ 2 replies \ @moptosh 13h \ parent \ on: Peter Wuille post about dropping OP_RETURN limit bitcoin
So, to summarize: Running a "bitcoin-d" node exposed on port 8333 behind a VPN that allows port forwarding to maintain anonymity.
write
preview
0 sats \ 1 reply \ @DarthCoin OP 13h
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
0 sats \ 0 replies \ @Fenix 5h
Ty for clarified I’m starting mine and I want to make it a real full node. I’m bookmarking it.
reply