pull down to refresh
0 sats \ 10 replies \ @DarthCoin OP 4h \ parent \ on: Some important aspects for node runners bitcoin
let me know when you can show me 100 or even more peers downloading blocks from your node, without opening the port 8333.
first you wrote personal nodes have no incoming connections, then you say max 8 is possible now if not 100 it's not ok. Makes no sense to me. Then I have seen yet a real world scenario where a onlynet tor and i2p node cannot sync the timechain.
reply
I said personal nodes are limited to max 8-10 peers. Is also written in Bitcoin documentation
read here: https://bitcoin.stackexchange.com/questions/8109/how-does-one-attain-1-000-connections-like-blockchain-info/8140#8140
Read more about Bitcoin P2P networking here: https://developer.bitcoin.org/devguide/p2p_network.html
Then I have seen yet a real world scenario where a onlynet tor and i2p node cannot sync the timechain.
Nobody said that if your node is on Tor network will not sync. Will only be limiting the INBOUND connections to 8.
Do you ever used torrents? Bitcoin blockchain works almost the same as torrents.
In your torrent client you can open to limited peers to seed or to everybody. You can also limit the bandwidth and/or IPs./networks.
You can still download the torrent even if you do not open any port for seeding. That means you are only a leecher. Once you start opening to share more the torrent to multiple peers, then you became a seeder. For more seeders will have the torrent, faster will be downloaded and kept alive.
reply
you wrote "the difference between a "personal node" (aka unreachable) and a "full node" (aka reachable)?" and
"I wonder how many of those Umbrel/Start9/mynodes/RPi nodes at home (also behind Tor) are real full nodes (reachable) that really help the network and relay properly."
implying that those "personal nodes behind tor" are not reachable. as you also wrote "our shity RPi unreachable node behind Tor".
So your info is not correct, as those rpi and etc personal nodes behind tor can be rrachable and have inbound connections even more than 8. I am nor sure why your're spreading false information, but that's on you.
reply
reachable means port 8333 open, it means more than 8 default limit peers that can download from your node.
non-reachable means port 8333 closed. All Tor nodes cannot open port 8333. Tor do not use ports.
reply
o tor node does not need to open port 8333 in order to seed or connect to other nodes, including clearnet nodes, althought seed from a tor node will be slower but still still possible.
reply
still limited to 8 peers
reply
take a look at this other one:
bitcoin-cli -netinfo
Bitcoin Core client v28.1.0 - server xxxxx/Satoshi:28.1.0/
onion i2p npr total block
in 15 12 1 28
out 8 2 0 10 2
total 23 14 1 38
reply
that's not reality, you can have much more than 8, as I just showed I am connect to 18 and it's a very bad internet connection lol
reply
as I said, connected doesn't mean are also downloading blocks. It could be very easily just pinging your node and waiting for response until one of the leechers are getting kicked out.
Also you will have to "announce" your node with
externalip=yourP2pTorHiddenService.onion or clearnet IP
listen=1