Bitcoin VerityOpen comparator

Level 9 · Advanced technical layer

P2P network, compact blocks and encrypted transport

How peers discover and relay data, how compact blocks save bandwidth and what BIP 324 does not hide.

Article
94
Reading time
15 minutes
Reviewed
10 September 2026

In a nutshell

Bitcoin nodes learn about transactions and blocks through a peer-to-peer network, but verify them locally. Compact block relay reconstructs a block from transactions already in a node's mempool; BIP 324 encrypts transport without normally authenticating a peer's real identity.

01

Peers exchange announcements

Nodes find peers through configured addresses, DNS seeds and addresses learned from the network. Inventory and related messages advertise objects before data is requested. Receiving the same block from many peers does not waive local validation.

02

Compact blocks reuse known data

BIP 152 sends a header, short transaction identifiers and selected prefilled transactions. The receiver reconstructs most of the block from its mempool and requests missing items; differing mempools can require another round or the full block.

03

Encrypted transport has a boundary

BIP 324 v2 protects P2P message contents and makes passive identification and active tampering harder. Ordinary connections do not prove a civil identity and the network layer still exposes endpoints such as IP addresses.

04

Connection diversity matters

An eclipse attacker tries to control all information reaching a node. Diverse inbound and outbound peers, networks and address groups make isolation harder. Encryption alone cannot help if the attacker is the peer at the end of the connection.

Level 9 · Advanced technical layer

Terms to know

Peer
Another node with a direct P2P connection.
Compact block
A block announcement built mostly from short IDs of transactions a peer may know.
Eclipse attack
Isolating a node behind connections controlled by an attacker.

Common misconception

An encrypted P2P link proves the peer's identity and makes the node anonymous.

A more accurate explanation

BIP 324 protects transport content but normally neither authenticates identity nor hides network endpoints.

A more accurate explanation

Why use several peers?

Independent connections improve propagation and reduce dependence on one view. The node still accepts only data that passes its own rules.

94

Key takeaways

  1. 01Peers carry data; they do not decide for your node.
  2. 02Compact blocks reuse mempool transactions.
  3. 03BIP 324 encrypts transport, not identity.
  4. 04Peer diversity reduces isolation risk.

A child-friendly recap

In very simple terms

Bitcoin computers send blocks and transactions directly to peers. Compact blocks mostly send short labels for known payments, while encryption protects messages rather than providing complete anonymity.

Reviewed: 10 September 2026

Sources and further reading

Sources support particular facts and definitions; listing one does not mean the editors endorse every view of its author.

01
Bitcoin Developer Guide: P2P networkBitcoin Developer Guide
developer.bitcoin.org
02
BIP 152: compact block relayBitcoin Improvement Proposals
bips.dev
03
BIP 324: v2 encrypted transportBitcoin Improvement Proposals
bips.dev

Educational material, not an investment recommendation.