Bitcoin Forum
May 09, 2024, 10:54:24 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: I'm in with BIP148 Segwit Node, But No Relay So Far on Blockchain.info  (Read 826 times)
ardacik (OP)
Sr. Member
****
Offline Offline

Activity: 259
Merit: 250

Bitcoin Freak


View Profile
June 08, 2017, 05:19:56 AM
Last edit: June 08, 2017, 07:39:03 AM by ardacik
 #1

Hello guys;

Just installed ubuntu server side bitcoin node. It was synced %100 blocks and not on blocksonly mode.

So the thing is my node have not made any relay yet. When i check on 21.co's other nodes, they are making relays on blockchain.info

How can i solve that issue, and make sure that it's working.

Thank you!
According to NIST and ECRYPT II, the cryptographic algorithms used in Bitcoin are expected to be strong until at least 2030. (After that, it will not be too difficult to transition to different algorithms.)
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
June 08, 2017, 06:55:33 AM
 #2

What do you mean by "no relays"?

You are relaying blocks and transactions to all nodes that you are connected to, regardless of whether the connection is inbound or outbound.

What you probably mean is that you can reach your node, so you are not accepting incoming connections. That, in itself, is not an issue. In order to accept incoming connections, you need to open up port 8333 on any firewalls you have (computer, router, etc.). That is all you need to do.

ardacik (OP)
Sr. Member
****
Offline Offline

Activity: 259
Merit: 250

Bitcoin Freak


View Profile
June 08, 2017, 07:12:28 AM
 #3

What do you mean by "no relays"?

You are relaying blocks and transactions to all nodes that you are connected to, regardless of whether the connection is inbound or outbound.

What you probably mean is that you can reach your node, so you are not accepting incoming connections. That, in itself, is not an issue. In order to accept incoming connections, you need to open up port 8333 on any firewalls you have (computer, router, etc.). That is all you need to do.

So just TCP 8333 is opened not UDP.. Should both of them must be enabled?

If so how can i enable UDP on ubuntu ssh?
ardacik (OP)
Sr. Member
****
Offline Offline

Activity: 259
Merit: 250

Bitcoin Freak


View Profile
June 08, 2017, 07:16:11 AM
 #4

What do you mean by "no relays"?

You are relaying blocks and transactions to all nodes that you are connected to, regardless of whether the connection is inbound or outbound.

What you probably mean is that you can reach your node, so you are not accepting incoming connections. That, in itself, is not an issue. In order to accept incoming connections, you need to open up port 8333 on any firewalls you have (computer, router, etc.). That is all you need to do.


https://blockchain.info/ip-address/195.244.58.186

Just like that. Other bitcoin nodes are giving some relay on blockchain networks. But mine does not
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
June 08, 2017, 07:50:10 AM
 #5

So just TCP 8333 is opened not UDP.. Should both of them must be enabled?

If so how can i enable UDP on ubuntu ssh?
What you should be checking is your router, not the firewall on your computer. Since the program opens up the port, you shouldn't need to do any extra configuring on the computer unless you have specifically set up such firewalling rules.

Only TCP is necessary.

https://blockchain.info/ip-address/195.244.58.186

Just like that. Other bitcoin nodes are giving some relay on blockchain networks. But mine does not
The nodes that are connected to blockchain.info is not the definitive list of all nodes. Bitnodes.21.co's list of reachable nodes likewise is also not definitive as their crawler also doesn't necessarily reach all nodes (although it is designed to do that).B

lockchain.info's "relayed by" field is completely irrelevant and useless. They only show the node that is connected to them that first relayed the transaction to them. Even if your node is connected to theirs (and I highly doubt it, they only have a hundred or so nodes connected), you won't necessarily have anything listed for "relayed" if all of the other nodes they are connected to relay the transaction to them before you do.

If Bitcoin Core reports that you have more than any number of incoming connections, then you are accepting incoming connections and are fine. You don't have to be listed on any site like bitnodes in order to be accepting incoming connections.

ardacik (OP)
Sr. Member
****
Offline Offline

Activity: 259
Merit: 250

Bitcoin Freak


View Profile
June 08, 2017, 08:05:14 AM
 #6

So just TCP 8333 is opened not UDP.. Should both of them must be enabled?

If so how can i enable UDP on ubuntu ssh?
What you should be checking is your router, not the firewall on your computer. Since the program opens up the port, you shouldn't need to do any extra configuring on the computer unless you have specifically set up such firewalling rules.

Only TCP is necessary.

https://blockchain.info/ip-address/195.244.58.186

Just like that. Other bitcoin nodes are giving some relay on blockchain networks. But mine does not
The nodes that are connected to blockchain.info is not the definitive list of all nodes. Bitnodes.21.co's list of reachable nodes likewise is also not definitive as their crawler also doesn't necessarily reach all nodes (although it is designed to do that).B

lockchain.info's "relayed by" field is completely irrelevant and useless. They only show the node that is connected to them that first relayed the transaction to them. Even if your node is connected to theirs (and I highly doubt it, they only have a hundred or so nodes connected), you won't necessarily have anything listed for "relayed" if all of the other nodes they are connected to relay the transaction to them before you do.

If Bitcoin Core reports that you have more than any number of incoming connections, then you are accepting incoming connections and are fine. You don't have to be listed on any site like bitnodes in order to be accepting incoming connections.

But the thing is blockchain.info captures all transactions right? If so they must be able to capture my ip address too? If i have connections on my node, that means i'm relaying some transactions. So which are they? I want to see them:)
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
June 08, 2017, 08:45:39 AM
 #7

Quote from: ardacik link=topic=1956475.msg19432953
But the thing is blockchain.info captures all transactions right? If so they must be able to capture my ip address too? If i have connections on my node, that means i'm relaying some transactions. So which are they? I want to see them:)
No, that is completely incorrect. Transactions have nothing to do with IP addresses. Blockchain.info is just one node among many thousands. They are not the actual bitcoin blockchain nor are they special in any way whatsoever.

Bitcoin uses a gossip protocol; when someone makes a transaction, they send it to the nodes they are connected to who then send the transaction to other nodes that they are connected, and so on and so forth. The process of receiving a transaction from one node and sending it to the other nodes you are connected to is called relaying. None of that involves IP addresses​ except for opening the connection between two nodes, which is done before any relaying happens and typically stays open after a transaction has been relayed.

ardacik (OP)
Sr. Member
****
Offline Offline

Activity: 259
Merit: 250

Bitcoin Freak


View Profile
June 08, 2017, 03:55:42 PM
 #8

Quote from: ardacik link=topic=1956475.msg19432953
But the thing is blockchain.info captures all transactions right? If so they must be able to capture my ip address too? If i have connections on my node, that means i'm relaying some transactions. So which are they? I want to see them:)
No, that is completely incorrect. Transactions have nothing to do with IP addresses. Blockchain.info is just one node among many thousands. They are not the actual bitcoin blockchain nor are they special in any way whatsoever.

Bitcoin uses a gossip protocol; when someone makes a transaction, they send it to the nodes they are connected to who then send the transaction to other nodes that they are connected, and so on and so forth. The process of receiving a transaction from one node and sending it to the other nodes you are connected to is called relaying. None of that involves IP addresses​ except for opening the connection between two nodes, which is done before any relaying happens and typically stays open after a transaction has been relayed.

my node is now just making upload, it that normal?
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
June 08, 2017, 04:21:41 PM
 #9

my node is now just making upload, it that normal?
What do you mean by "making upload"?

ardacik (OP)
Sr. Member
****
Offline Offline

Activity: 259
Merit: 250

Bitcoin Freak


View Profile
June 09, 2017, 05:50:57 AM
 #10

my node is now just making upload, it that normal?
What do you mean by "making upload"?

I mean there is just an outgoing traffic on my server, not any incoming ones.
ranochigo
Legendary
*
Online Online

Activity: 2968
Merit: 4177



View Profile
June 09, 2017, 09:34:01 AM
 #11

my node is now just making upload, it that normal?
What do you mean by "making upload"?

I mean there is just an outgoing traffic on my server, not any incoming ones.
Its normal. Bitcoin traffic is bidirectional. That means a incoming connection will receive data from you and send data to you.

If you want to check if you can accept connection, go to canyouseeme.org and put the port as 8333. If they can see you, the port is open. Go to bitnodes.21.co, scroll down and verify your node.

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!