I understand that the AS information plays a part in how addresses are populated in the new table for IPv4/IPv6 addresses, but how does it work for .onion addresses?

I understand the address assignment for IPv4/IPv6 via (https://github.com/bitcoin/bitcoin/blob/505ba3966562b10d6dd4162f3216a120c73a4edb/src/addrman.h#L57) but the process for .onion address is not clear to me. The only thing I know is that the group for the .onion address is the first 4 bytes of the address(without the .onion)

Hi,

Does anyone know if we can run multiple hidden services on 1 bitcoin node? I am planning to set up a bitcoin node with 10's of hidden services.
I know that I would manually have to create them, but I am not clear on the port situation for these services.

Hi,

I am aware that the IP address has a group which is the /16 address, but what is the group that is assigned to onion addresses?

For more details on this topic, please refer to https://eprint.iacr.org/2015/263.pdf page 4.

I wanted to get details on the contents of the addr messages from a IP node to a TOR node and vice versa. I was able to connect by installing tor and then restarting bitcoin core. It automatically creates a hidden service for me without having to change the config file.

Hi,
I am running a pruned IP node and a pruned TOR node. How do I connect to the TOR node from the IP node?

Thing is, for some connections it is the IP address of my machine, whereas for others it is the localhost. Just curious to find out what the differences could be.

It's weird that you have both IPv4 and Tor connections. Do the IPv4 allow incoming connections? Try setting listen=0.

I set up my bitcoin node to run over tor with the following in the config file
# Core
conf=<some_path>/.bitcoin/bitcoin.conf
server=1
daemon=1
prune=23552
maxconnections=1000

# TOR
proxy=127.0.0.1:9050
listenonion=1
listen=1
onlynet=onion

#RPC
rpcuser=username
rpcpassword=password

Question 1 :
I see some inbound connections that have IPv4 addresses. These IPv4 addresses do not show up on bitnodes, so I am a bit curious as to what these addresses are.

Question 2:
Is my node running both on IP and TOR?

Question 3:
If I understand correctly when running a node on TOR, DNS seeders are not utilized and it defaults to the harcoded list of .onion addresses. My first outbound peer was not in the list of addresses in the file. Where could this have come from?

Question 4:
I have what is the difference between onion and not_publicly_routable  in the network fields ?

I was of the idea that the information from bitnodes is reliable. But that changed when I looked closely into the information I get from running my node.
There are IP addresses in the addr field for outbound connections appear in the list of nodes they crawl every 6 min, but there are IP addresses in the addr field of inbound connections that do not appear on bitnodes. Does anyone have an idea what these entities are? (if they are not nodes?)

Additionally, some peers have the addrlocal field set to 127.0.0.1, while most have my IP address. Any reason why?

So what would the configuration look like if I want to run the bitcoin node over clearnet and on TOR?

So basically, if a machine runs TOR and bitcoind at the same time, without me making any configurations to the .conf file, it will by default be on the TOR network?
So is my node a combination of IP and TOR? Under what circumstance would someone opt for this?

Hi,
My bitcoin.conf looks like this

# Core
conf=/root/.bitcoin/bitcoin.conf
server=1
daemon=1
prune=23552
maxconnections=1000

# TOR
#proxy=127.0.0.1:9050
#bind=127.0.0.1
#listen=1
#listenonion=1
#onlynet=onion
#dnsseed=0

#RPC
rpcuser=username
rpcpassword=password


from when I moved over from my node running over TOR.
Problem is, my node still has outgoing connections to .onion addresses and not to IP addresses. When I type bitcoin-cli -getinfo, the proxies field says 127.0.0.1(9050)
I have no idea how my node is functioning right now(IP or onion). Can anyone explain this behaviour?

Hi,
I have a pruned BTC node running over TOR with onlynet= onion and upon startup this node has 10 outgoing connections all to onion addresses. Question is, where does the node get the onion addresses from?
I understand that there are DNS seeders for bitcoin, but do they return onion addresses if they detect that the requesting node is running bitcoin over tor?
Also, I know that there is a list of hardcoded onion addresses in bitcoin core and I have observed that at times, the first outgoing connection is not from that list of nodes. Anyone have any idea why?


Additionally, what do you think would be the merits/demerits of running a node on both TOR and IP?
I'm trying to cover all grounds because I am collecting information of the current topology of the network and would like to have a complete view of the network. Any suggestions would be really appreciated.

Thank you for your replies. This sure does help my understanding of connections for my tor node.

I am running a pruned bitcoin node that is running onlynet = onion.
Using the bitcoin-cli I get the list of IP addresses for incoming connections and I can see that there are ipv4 addresses in there. How does that really work? I'm guessing it is a 6 hop circuit because my bitcoin node is a hidden service. If that is the case, then the ipv4 address should not be visible.

I'm sure there is a gap in my understanding for incoming connections and I would really appreciate it if someone could clarify it.

Facing the same problem. Differences are that I am running a pruned node.
Were you able to move forward with the inbound connections?

Hi,

How would I go about accessing the new and tried tables in my bitcoin node?

Hi all,

I am trying to figure out the source node of a propagated transaction in the bitcoin network. My approach is to set up multiple nodes and analyze the received transactions.
Additionally, I was curious on what I need to do to connect to a bitcoin node running tor(I'm guessing I have to configure the SOCKS5 proxy). After the TOR configuration can I just add a peer with their .onion address?
I am also planning to set the maximum connections to say 1000 per node. I was told this is a bad idea because it will slow down processing at my node if I don't have enough resources, but it seems like a good way to get transactions from multiple nodes.
Any ideas and opinions will be highly appreciated.