Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryPrivacy2019Design paperCorpus record

Version 2 P2P Encrypted Transport Protocol

BIP 324. Dhruv Mehta, Tim Ruffing, Jonas Schnelli and Pieter Wuille.

A v2 connection does an Elligator-style handshake and then encrypts the byte stream, so a passive observer cannot read the messages or easily identify the protocol.

A reading of the public document. Not a copy of it, and not a claim about a later network that reused the name.

A privacy claim about the peer network should say whether it is this transport, a VPN, or a change to what is announced.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
1

Code

Source, repository, and what is actually hosted

  • BIP 324https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki
  • bitcoin/bipsRepository taken from the source URL. 97 other studies in this library cite the same repository. This is not an audit.
  • Full upstream textMirrored 2026-10-10 under BSD-3-Clause. The desk study is not part of that licence.
  • Add to a reading list

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    Bitcoin's peer protocol was unencrypted. A network observer could see which transactions a node announced and which blocks it requested.

  2. Claim 02 · Paper model

    The rule

    A v2 connection does an Elligator-style handshake and then encrypts the byte stream, so a passive observer cannot read the messages or easily identify the protocol.

  3. Claim 03 · Paper model

    How it is put together

    The handshake is unauthenticated against an active man in the middle, unless a later authentication is added. Encryption here is against passive surveillance. The content of the chain does not become private.

  4. Claim 04 · Paper model

    Where the claim stops

    This does not hide which IP you connect to.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    Bitcoin's peer protocol was unencrypted. A network observer could see which transactions a node announced and which blocks it requested.

    Model

    What has to hold

    This does not hide which IP you connect to.

    Falsifier

    What would retire it

    What can a passive observer still see?

  2. 02 The rule

    Observation

    What the study says

    A v2 connection does an Elligator-style handshake and then encrypts the byte stream, so a passive observer cannot read the messages or easily identify the protocol.

    Model

    What has to hold

    An active attacker who intercepts the handshake can still sit in the middle.

    Falsifier

    What would retire it

    What can a passive observer still see?

  3. 03 How it is put together

    Observation

    What the study says

    The handshake is unauthenticated against an active man in the middle, unless a later authentication is added. Encryption here is against passive surveillance. The content of the chain does not become private.

    Model

    What has to hold

    An active attacker who intercepts the handshake can still sit in the middle.

    Falsifier

    What would retire it

    Does the handshake authenticate the peer?

  4. 04 Where the claim stops

    Observation

    What the study says

    This does not hide which IP you connect to.

    Model

    What has to hold

    This does not hide which IP you connect to.

    Falsifier

    What would retire it

    Is the session encrypted?

03 Sequence

One action, as an operating tape

  1. 01Open a connection.
  2. 02Complete the v2 handshake.
  3. 03Send the same logical messages inside the encrypted stream.
  4. 04Is the session encrypted?

04 Load-bearing

The argument, and where a pitch drops it

  1. Why it is still on the desk

    The cut

    A privacy claim about the peer network should say whether it is this transport, a VPN, or a change to what is announced.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

  2. After the text

    The cut

    Bitcoin Core shipped v2 transport as optional and then as a default direction. The BIP is the handshake.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    An active attacker who intercepts the handshake can still sit in the middle.

05 Register

What has to be true

  • Model · Not re-measured

    This does not hide which IP you connect to.

  • Model · Not re-measured

    An active attacker who intercepts the handshake can still sit in the middle.

  • Model · Not re-measured

    It is not Tor, and not a mixnet.

06 Divergence

What happened after the paper

Bitcoin Core shipped v2 transport as optional and then as a default direction. The BIP is the handshake.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  4. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

Bitcoin's peer protocol was unencrypted. A network observer could see which transactions a node announced and which blocks it requested.

What the design proposes

  • The handshake is unauthenticated against an active man in the middle, unless a later authentication is added.
  • Encryption here is against passive surveillance.
  • The content of the chain does not become private.

How the mechanism is specified

  • Open a connection.
  • Complete the v2 handshake.
  • Send the same logical messages inside the encrypted stream.

What this page does not treat as proven

  • This does not hide which IP you connect to.
  • An active attacker who intercepts the handshake can still sit in the middle.
  • It is not Tor, and not a mixnet.

Why the desk still reads it

A privacy claim about the peer network should say whether it is this transport, a VPN, or a change to what is announced.

09 Lexicon

Terms, opened into the record

v2 transport
The encrypted Bitcoin peer protocol.
Passive observer
A party who can read packets but not change them.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

Protocols

Upstream

The file, in full

Licence recorded on the mirror: BSD-3-Clause. Canonical file: https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki. Numbers and web addresses in the file open a study or the address itself.

Loading the mirrored file.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.