<p>Even if both peers support BIP324, the initiator of the connection might not have known that the acceptor did. Bitcoin Core (as of v27) has downgrading logic (i.e., it will retry with v1 if a v2 connection fails in some circumstances), but no upgrade logic (it will not automatically reconnect when a v1 peer tells it it supports v2).</p>
<p>My best guess is simply that your peer did not have up-to-date &quot;addr&quot; information about your node.</p>

CC BY-SA 4.0
2024-04-24T14:46:13.707Z
2024-04-24T14:54:16.350Z
2024-04-24T14:54:16.350Z
Pieter Wuille
<p>Bitcoin Core 27.0 which enables v2 transport (BIP324) by default was released a few days ago. I'm already seeing a few peers with the /Satoshi:27.0.0/ user agent and all of them have the P2P_V2 service flag set. However, one of the peers (inbound) is connected over a v1 connection. Is this evidence of network tampering (as failed v2 connections retry as v1), or could there be another reason?</p>

CC BY-SA 4.0
2024-04-24T13:47:54.227Z
What version are you running?
Murch
CC BY-SA 4.0
2024-04-24T14:18:54.493Z
27.0, but I don't think there's any difference from 26.0 with respect to BIP324 except for the changed default, right?
Vojtěch Strnad
<bitcoin-core><network><bip324-p2p-encryption>
Why is my P2P_V2 peer connected over a v1 connection?
Vojtěch Strnad
# Why is my P2P_V2 peer connected over a v1 connection?

(Asked by: username_0 on 2024-04-24)

Bitcoin Core 27.0 which enables v2 transport (BIP324) by default was released a few days ago. I'm already seeing a few peers with the /Satoshi:27.0.0/ user agent and all of them have the P2P\_V2 service flag set. However, one of the peers (inbound) is connected over a v1 connection. Is this evidence of network tampering (as failed v2 connections retry as v1), or could there be another reason?

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

> **Comments:**
> **username_1**: What version are you running?  
> **username_0**: 27.0, but I don't think there's any difference from 26.0 with respect to BIP324 except for the changed default, right?  

---

## 1 answers

### Answer by username_2 on 2024-04-24. Score: 7 | Accepted answer

Even if both peers support BIP324, the initiator of the connection might not have known that the acceptor did. Bitcoin Core (as of v27) has downgrading logic (i.e., it will retry with v1 if a v2 connection fails in some circumstances), but no upgrade logic (it will not automatically reconnect when a v1 peer tells it it supports v2).

My best guess is simply that your peer did not have up-to-date "addr" information about your node.


---

