pull down to refresh
20 sats \ 32 replies \ @88b0c423eb 3h \ on: Some important aspects for node runners bitcoin
"A Bitcoin node is considered as a reachable node if it accepts incoming connections from its peers."
So if one has incoming connections, but only from tor and i2p it's still considered a reachable node, right?
$ bitcoin-cli -netinfo
Bitcoin Core client v28.2.0 - server 70016/Satoshi:28.2.0/
in 13 5 1 19
out 7 3 0 10 2
total 20 8 1 29
reply
Yes, but is limited only to those networks and specific peers, not the whole network.
Here is another interesting explanation by Eric Voskuil
(source: https://xcancel.com/evoskuil/status/1960721620273684618)
Some people are better with observation than theory, and need to think through problems by way of examples.
So consider a case where there are 100 million full nodes, and only 100 of them support all economic activity in the world. All others only validate and relay valid blocks.
To function, the 100 do not require the others. They require only to obtain blocks, which of course arise only from each other. They connect and relay with the others, but get no actual information from them.
At some point the others all decide to hard fork, resulting in their nodes rejecting the 100’s blocks. The 100 continue to operate unaffected.
Or at some point the 100 decide to hard fork, resulting in the others rejecting their blocks. The 100 continues to operate unaffected.
Now consider the case in which economic activity, measured as the value of coin being accepted in trade on average over time, is evenly distributed among the 100. And in the case where the 100 hard forks, 1 of them (representing 1% of their economy) decides to not adopt the fork. This one remains with the others, the 99% continue. Also consider a scenario where 99% reject the fork, and 1 forks himself off.
In these cases, the 1 has 1% of the economic power, to either compel a fork, or resist one, and the 99 have 99%. This is not hash power, this is economic power. There is no implied majority control outcome, but there is outcome driven by power.
And now consider the 999,999,900 other nodes. They have zero impact on either scenario. They are totally irrelevant. The 100 doesn’t benefit from them in any way. In fact, they end up representing a Sybil against the economy.
reply
This is what the configuration page looks like for an Umbrel node (out of the box) with their latest UI.
What should I be doing differently? Best I can tell I have ~ 50 peers over Clearnet/Tor/I2p but all my inbound connections appear to be Tor/I2p.
This is not the only node I run but it is the easiest to get 'configured' what do you think?
reply
@DarthCoin thinks it's best for you to use clearnet and forward port 8333 with a fixed public IP. Total nonsense.
reply
Best I can tell it's already configured... to connect over clearnet inbound to 'Listen'.
Right?
reply
Correct, using tor and i2p there's no need to open any port. i2p has no exit nodes so it will not conenct outside of i2p network, but tor will. I2p is much faster than tor though as every client is also a node.
reply
Why only the 100 support all economic activity in the world and the others million nodes don't?
reply
because those 100 nodes opened their inbound port.
reply
So lets say there are no more nodes with inbound port open, what happens then?
reply
then every node is limited to those 8 peers near by, even that the whole network is like 100k nodes.
Now ask yourself: what happen if you seed blocks from your node only to 8 peers, and you cannot get new blocks from others that are not in your network/area ? It means some nodes will not have the whole blockchain correctly seeding it. Quite a mess, right?
reply
but if even one of the tor/i2p nodes also accepts connections over ipv4/6, then the tor/12p nodes would still see the wider network through connection to that node - the config can allow any combination of connections to be active
reply
Do tor and i2p work only in my network/area?
reply
is more about your latency
reply
i2p is better than tor in that regard.
it's not only 8(connected to 18 rn) as you say and not limited by my area.
Each node behind Tor or 12p it falls under default rule of max 8 - 10 peers.
That means only max 8-10 other new nodes can IBD from you or others to sync latest blocks. Due to the latency of Tor and i2p half of those will get kicked from connection several times.
To have more inbound you must define that in bitcoin.con file and open the port 8333. But this imply to have a really good connection, good hardware, public IP, good networking knowledge etc. things that many Umbrel or Start9 users do not have.
Let's say you create in the end a network only with a bunch of 100 nodes over Tor, ok you sync from each others just fine. But in fact you are isolating yourself from the rest of the network. Think about that.
reply
You can much more than 8-10 peers over tor and i2p, I have 18 right now. But I could also use ipv4 and ipv6 over tor to connect to clearnet nodes without opening port 8333. Or am I missing something?
reply
If you are NOT "listening" on port 8333 (or can be any other you want) for inbound connections, your node will randomly kick out peers from those max 8-10 connections.
That doesn't mean your node is not working properly. No, is OK to not open the port 8333, only that your node is not a full public node, but just a personal node.
reply
you say max 8-10 connections, why I have 18 connections right now?
reply
how many of those 18 are really active, downloading from you? Just because are connected it doesn't mean that you are really seeding to them.
reply
but there are more nodes over tor and i2p than on clearnet afaik
reply