Why it exists
BIP 324 encrypts traffic between Bitcoin peers. It reduces what a passive network observer can learn from reading a node connection, while retaining Bitcoin’s open peer-to-peer model. It changes how messages travel, not how transactions and blocks are validated.
How it works
Peers establish session keys during a version-2 transport handshake and use them to encrypt and authenticate subsequent packets. The design avoids an obvious fixed handshake pattern and supports transport extensions. Separate traffic directions use distinct cryptographic state.
Encryption is opportunistic: the handshake does not certify a peer’s real-world identity. An actively interfering intermediary is a different threat from someone merely recording packets. Node software still needs to process untrusted messages and independently validate the Bitcoin data they contain.
A practical example
If your node connects to a compatible peer using v2, someone monitoring the link cannot simply read the clear-text transaction announcements as they could with v1. The peer itself still receives the messages, and a network observer can still see that your IP address is exchanging traffic with another address.
What to keep in mind
BIP 324 does not hide IP addresses, guarantee anonymity, or prevent a malicious peer from lying. It does not replace Tor or I2P where those solve a separate network-identity problem. Connections to peers without v2 support can still use v1.
Status & implementation
BIP 324 is Deployed. Bitcoin Core 27.0 enabled v2 transport by default, including attempts for manually configured peers with v1 fallback on failure. Actual transport depends on the connection and both peers’ capabilities.
Specification status: Deployed · Sources checked 13 November 2026
