Quote from: ranochigo on July 29, 2024, 12:07:43 PM

Quote from: Donald6680 on July 29, 2024, 11:52:10 AM

And one more question.
Should my port be on 8333?
I don't know what my current port is.
Why maps like this site: https://bitnodes.io/nodes/live-map/
It doesn't show anything in my country?

After clicking the check node option on the site, I received this error:
(My IP: 8333 is unreachable)

What does this mean? I'm not node?

You are a node. Nodes can either connect to others or let others connect to you. Assuming that you're not portforwarding 8333, then Bitcoin Core cannot accept incoming connections and other nodes cannot connect to you. However, you can still connect to others.

This doesn't impact your usability or utility in any way, but it would definitely be better if others could connect to you.

There is debate as to whether you are or are not a Full Node if you are not receiving incoming traffic. In my view, you are not an optimized Full Node if your incoming traffic is zero. But what I don't understand is this: What is the degree of support of consensus mechanism given Full Node with versus without incoming traffic? Anyone?

Here are some steps to configure incoming traffic.
1. Look on the label of your router/modem for the IP address of the device. Enter that into the address bar of your browser. The device's menu will load.
2. Go to Advanced and Port Forwarding. If your menu lacks Advanced/Port Forwarding, you must upgrade your modem. I had to do that with my telecom Altice in the Dominican Republic.
3. Enter 8333 in all fields and save. Reboot modem and computer.
4. Go to: bitnodes.io The site will recognize your IP address. Scroll down a bit and click search to see if you are recognized. I am a noob running the only BTC Full Node in the Dominican Rpublic
and Haiti for several years.