<p>With these bitcoin.conf parameters:</p>
<pre><code>proxy=127.0.0.1:9050
listen=1
onlynet=onion
bind=127.0.0.1
externalip=[my 64-char code].onion
[plus 32 addnode=[onion address] entries]
</code></pre>
<p>I quickly get 18 outgoing connections to .onion addresses (and never more, even after 24+ hours?), and then after a while one or two incoming addresses identified like this:</p>
<pre><code>127.0.0.1:57926 (node id: 40)
via 127.0.0.1:9050
</code></pre>
<p>or like this:</p>
<pre><code>127.0.0.1:58152 (node id: 78)
via akuserwyfe5ehl6i.onion:32645
</code></pre>
<p>or like this:</p>
<pre><code>127.0.0.1:58516 (node id: 189)
[that's it -- no &quot;via&quot;!]
</code></pre>
<p>What causes these node identification format variations?</p>

CC BY-SA 4.0
2021-09-02T20:33:05.553Z
Plus up to 2 block-only connections gives 18.
Pieter Wuille
<bitcoin-core><tor><connection>
Why variations in tor onion service incoming node identifcation formats?
brec
# Why variations in tor onion service incoming node identifcation formats?

(Asked by: username_0 on 2021-09-02)

With these bitcoin.conf parameters:
proxy=127.0.0.1:9050
listen=1
onlynet=onion
bind=127.0.0.1
externalip=[my 64-char code].onion
[plus 32 addnode=[onion address] entries]

I quickly get 18 outgoing connections to .onion addresses (and never more, even after 24+ hours?), and then after a while one or two incoming addresses identified like this:
127.0.0.1:57926 (node id: 40)
via 127.0.0.1:9050

or like this:
127.0.0.1:58152 (node id: 78)
via akuserwyfe5ehl6i.onion:32645

or like this:
127.0.0.1:58516 (node id: 189)
[that's it -- no "via"!]

What causes these node identification format variations?

**Tags:** bitcoin-core, tor, connection

> **Comments:**
> **username_1**: Plus up to 2 block-only connections gives 18.  

---

## 0 answers

