Author

Topic: The port should be 8333? (node) (Read 84 times)

newbie
Activity: 13
Merit: 12
July 30, 2024, 02:58:36 PM
#5
1, 2, 3. Port 8333 is correct regardless of pruned or not. 8333 is the default port, but in some cases (such as multiple nodes on the same local network), you might want to change it.
4. A pruned node stores only block information relevant to your wallet.
5. A full node provides block and transaction data to other nodes. I don't know specifically how being a pruned node affects the amount of outgoing data, but I imagine it reduces the amount significantly because you don't store the entire block chain.

For bitnodes, did you enter your node's local IP address, 192,168.x.x or 10.x.x.x, or did you enter the address for your local network?
Automatically detects my Internet IP address
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
July 30, 2024, 12:59:13 AM
#4
5. A full node provides block and transaction data to other nodes. I don't know specifically how being a pruned node affects the amount of outgoing data, but I imagine it reduces the amount significantly because you don't store the entire block chain.
Correct. In 200 days, my pruned bitcoind downloaded 330 GB and uploaded 937 GB. Before I had to prune it, it would upload 2 TB per month.
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
July 29, 2024, 06:41:05 PM
#3
If you are going to change the default port to non 8333 then you are not accepting connections from other nodes however, you can still connect to other nodes without accepting incoming data from other nodes.

The issue of IP is unreachable even if you use the default port 8333. It might be a firewall rule in your router or anything that blocks your node from accepting incoming connections from other nodes.
Try to follow the guide from the link below to set up your router.

- https://bitcoin.org/en/full-node#enabling-connections
legendary
Activity: 4466
Merit: 3391
July 29, 2024, 01:36:24 PM
#2
1, 2, 3. Port 8333 is correct regardless of pruned or not. 8333 is the default port, but in some cases (such as multiple nodes on the same local network), you might want to change it.
4. A pruned node stores only block information relevant to your wallet.
5. A full node provides block and transaction data to other nodes. I don't know specifically how being a pruned node affects the amount of outgoing data, but I imagine it reduces the amount significantly because you don't store the entire block chain.

For bitnodes, did you enter your node's local IP address, 192,168.x.x or 10.x.x.x, or did you enter the address for your local network?
newbie
Activity: 13
Merit: 12
July 29, 2024, 01:13:59 PM
#1
Hello.
I downloaded the entire blockchain (600 gigs) and completed it. I chose the node type pruned, because I had no free space on the hard drive. And I think I am a node now.

Screenshot of bitcoin core status:
https://i.postimg.cc/nh1pQMHs/Screenshot-2024-07-29-212726.png
https://i.postimg.cc/RFLck79S/Screenshot-2024-07-29-212747.png

I have some questions and please help me:

1- Should my port be on 8333? I don't know what my current port is. Given that I am now a pruned node, do I need to be on port 8333?

2- If I want to be a full node in the future, should I be on port 8333?

3- What is the difference between being on port 8333 and not being on port 8333?

4 - What is the difference between full node and pruned? Is full node good and does it help the network more? Is pruned worthless?

5 - I read this on bitcoin.org:It's common for full nodes on high-speed connections to use 200 gigabytes upload or more a month. Download usage is around 20 gigabytes a month. Is this for full nodes on port 8333 or all full nodes? How much is the consumption of pruned nodes?

i visit https://bitnodes.io/#join-the-network and After clicking the check node option on the site, I received this error:
(My IP:8333 is unreachable)
I did everything mentioned in the links below:
https://bitcoin.org/en/full-node#network-configuration --- https://bitcoin.org/en/full-node#port-forwarding and
https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/create-an-inbound-port-rule.

I'm sorry it took so long.
thank you very much ❤️
Jump to: