BIP-324 specifies version 2 of Bitcoin’s peer-to-peer (P2P) transport protocol, adding opportunistic encryption to connections between nodes. Its purpose is to make passive eavesdropping and simple identification of Bitcoin traffic harder while carrying the same kinds of network messages between peers.
How it works
Two nodes that support version 2 negotiate a connection and establish shared transport keys before exchanging Bitcoin application messages. The protocol encrypts message contents and makes the bytes on the connection less recognizable to a passive observer. BIP-324 is deployed, and compatible nodes can still accept inbound version 1 connections for interoperability with older peers.
This is a transport-layer change to Bitcoin’s peer-to-peer network. It does not change transaction validity, consensus rules, or the public contents of the blockchain.
Scope and limitations
The encryption is opportunistic and unauthenticated: it does not prove the identity of the remote node or stop an active attacker from attempting a man-in-the-middle or downgrade attack. It also does not make Bitcoin transactions private. Network observers may still learn connection endpoints, timing, or other traffic metadata, and the transactions relayed remain public data.
Why it matters
Encrypting node connections can reduce passive visibility into peer-to-peer traffic and make the protocol less trivial to fingerprint. That can improve transport privacy, but it is one network-layer protection rather than a substitute for transaction privacy or a guarantee of anonymity.
History
- 2019 — BIP-324 was authored and submitted. The BIP currently lists its status as Deployed.
Common Misconceptions
“BIP-324 makes Bitcoin transactions private.” It encrypts supported node-to-node transport. Transactions relayed through the network remain public, and the encrypted connection does not prove the remote peer’s identity.
Criticisms
- The protocol does not authenticate peers, so encryption alone cannot rule out an active man-in-the-middle or downgrade attempt.
- Connection endpoints, timing, and other traffic patterns may still reveal metadata.
Social Media Sentiment
In sampled r/Bitcoin discussions, users welcome making passive surveillance harder, while recurring questions show confusion about whether the encrypted messages are the Bitcoin transactions themselves. Replies distinguish transport privacy from transaction privacy and discuss compatibility with older nodes. These threads are historical examples, not a measure of current adoption.
Last updated: 2026-10
Related terms
See Also
Sources
- BIP-324 specification — documents the deployed version 2 transport, its opportunistic encryption, and compatibility behavior.
- Bitcoin Core 26.0 release notes — documents the initial experimental support for BIP-324 v2 transport and its per-connection negotiation.
- r/Bitcoin discussion about running a BIP-324 node — a sampled community thread with questions about optional support, privacy scope, and compatibility.