<p>There is currently no way to specify the v2transport option for the <code>-addnode</code> startup option.</p>

CC BY-SA 4.0
2023-12-20T16:33:45.710Z
Note that there is a PR open to make all manual (addnode/connect) connections attempt v2: https://github.com/bitcoin/bitcoin/pull/29058 implicitly. If that lands, in 27.0 you won't need to specify anything.
Pieter Wuille
CC BY-SA 4.0
2023-12-20T19:42:37.917Z
Does it mean that with `v2transport=1` in `bitcoin.conf` it will not be necessary to specify any `v2transport` arguments for each pair added with `addnode=` in `bitcoin.conf` since it will always attempt the negotiation using **P2P v2** first of all?
Thanks for your answer
2F4kT0r
CC BY-SA 4.0
2023-12-20T20:22:45.747Z
@2F4kT0r If that PR makes it into 27.0, then yes, with 27.0 (expected release around April 2024) you will not need to specify.
Pieter Wuille
CC BY-SA 4.0
2024-01-17T08:24:05.497Z
Merged! https://github.com/bitcoin/bitcoin/pull/29239 + https://github.com/bitcoin/bitcoin/pull/29058

Thanks!
2F4kT0r
CC BY-SA 4.0
2023-12-20T15:38:11.453Z
2023-12-20T15:38:11.453Z
Ava Chow
<p>I'm trying to use the new <strong><code>v2transport</code></strong> argument on <code>addnode=</code> in <code>bitcoin.conf</code> to attempt to connect to the peer using BIP324 v2 transport protocol.</p>
<p>I tried using, for example, the <code>bitcoin-cli addnode &quot;192.168.1.94:8333&quot; &quot;add&quot; true</code> command, and it worked.</p>
<p><a href="https://i.sstatic.net/yslJn.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/yslJn.png" alt="enter image description here" /></a></p>
<p><a href="https://i.sstatic.net/1GU3g.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/1GU3g.png" alt="enter image description here" /></a></p>
<pre><code>bitcoind[935]: 2023-12-14T12:28:33Z New manual v2 peer connected: version: 70016, blocks=2542818, peer=7
</code></pre>
<p>Now, I want to use it by adding it to the <code>bitcoin.conf</code> file to get persistent configuration and always exec this at startup, but any combination that I try, works for me, the connection with the peer always fails.</p>
<p>Someone knows if this feature was added with v26.0 or not and if yes, what nomenclature I should use to get this?</p>
<p>Refs:</p>
<p><a href="https://github.com/bitcoin/bitcoin/pull/28331" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/pull/28331</a></p>
<p><a href="https://bitcoincore.org/en/releases/26.0/" rel="nofollow noreferrer">https://bitcoincore.org/en/releases/26.0/</a></p>
<p><a href="https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-26.0.md#updated-rpcs" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-26.0.md#updated-rpcs</a></p>
<p><a href="https://bitcoincore.org/en/doc/26.0.0/rpc/network/addnode/" rel="nofollow noreferrer">https://bitcoincore.org/en/doc/26.0.0/rpc/network/addnode/</a></p>
<p><a href="https://i.sstatic.net/GoOZ1.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/GoOZ1.png" alt="enter image description here" /></a></p>

<bitcoin-core><peers><bip324-p2p-encryption>
addnode + v2transport (BIP324) argument available to the bitcoin.conf?
2F4kT0r
# addnode + v2transport (BIP324) argument available to the bitcoin.conf?

(Asked by: username_0 on 2023-12-20)

I'm trying to use the new **`v2transport`** argument on `addnode=` in `bitcoin.conf` to attempt to connect to the peer using BIP324 v2 transport protocol.

I tried using, for example, the `bitcoin-cli addnode "192.168.1.94:8333" "add" true` command, and it worked.

[![enter image description here](https://i.sstatic.net/yslJn.png)](https://i.sstatic.net/yslJn.png)

[![enter image description here](https://i.sstatic.net/1GU3g.png)](https://i.sstatic.net/1GU3g.png)

```
bitcoind[935]: 2023-12-14T12:28:33Z New manual v2 peer connected: version: 70016, blocks=2542818, peer=7

```

Now, I want to use it by adding it to the `bitcoin.conf` file to get persistent configuration and always exec this at startup, but any combination that I try, works for me, the connection with the peer always fails.

Someone knows if this feature was added with v26.0 or not and if yes, what nomenclature I should use to get this?

Refs:

<https://github.com/bitcoin/bitcoin/pull/28331>

<https://bitcoincore.org/en/releases/26.0/>

<https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-26.0.md#updated-rpcs>

<https://bitcoincore.org/en/doc/26.0.0/rpc/network/addnode/>

[![enter image description here](https://i.sstatic.net/GoOZ1.png)](https://i.sstatic.net/GoOZ1.png)

**Tags:** bitcoin-core, peers, bip324-p2p-encryption


---

## 1 answers

### Answer by username_1 on 2023-12-20. Score: 3

There is currently no way to specify the v2transport option for the `-addnode` startup option.

> **Comments:**
> **username_2**: Note that there is a PR open to make all manual (addnode/connect) connections attempt v2: https://github.com/bitcoin/bitcoin/pull/29058 implicitly. If that lands, in 27.0 you won't need to specify anything.  
> **username_0**: Does it mean that with `v2transport=1` in `bitcoin.conf` it will not be necessary to specify any `v2transport` arguments for each pair added with `addnode=` in `bitcoin.conf` since it will always attempt the negotiation using **P2P v2** first of all? Thanks for your answer  
> **username_2**: @username_0 If that PR makes it into 27.0, then yes, with 27.0 (expected release around April 2024) you will not need to specify.  
> **username_0**: Merged! https://github.com/bitcoin/bitcoin/pull/29239 + https://github.com/bitcoin/bitcoin/pull/29058  Thanks!  

---

