RoadmapsProjects
Sign in./start

Learn

RoadmapsProjects

Contribute

DiscoverIssues

Account

Sign in./start-building

Become an Open Source Builder. Learn. Build. Contribute.

Learn

RoadmapsProjectsStart Building

Contribute

DiscoverIssues

Account

Sign inDashboardSettings

Legal

PrivacyTerms

© 2026 Pull // all rights reserved

PrivacyTerms

lesson // bitcoin

P2P Adversarial Thinking

Eclipse attacks, topology leaks, compact block relay, and why Bitcoin’s gossip layer is a security surface.

advanced6 days

Public lesson — sign in to track progress on this roadmap.

./sign-in

On this page

Learning objectives

  • Explain eclipse and partitioning risks for Bitcoin peers
  • Describe what compact blocks optimize and what they do not secure
  • List practical defenses for node operators and wallet backends

study // plan

Lessons are primers. Depth comes from required reading, interactive labs, reflection, and a hands-on check with evidence — the BOSS study pattern.

Research on Bitcoin Search

Required reading

  • articleEclipse Attacks on Bitcoin’s Peer-to-Peer Network
  • bipBIP-152 Compact Block Relay
  • docsCompact Blocks FAQ

Reflection prompts

  1. How can an adversary isolate a node from honest peers, and what symptoms would you look for in logs?
  2. What problem do compact blocks solve, and which attack classes remain even with BIP-152?
  3. If you run infrastructure for wallets, which P2P settings and monitoring would you harden first?

Lab // Node exposure worksheet

Document your bitcoind (or Polar) peer settings — maxconnections, addnode/connect, onion vs clearnet — and write a short adversarial threat note for that setup.

evidence required

  • ·Export or screenshot of peer/connection config
  • ·Half-page threat note covering eclipse and DoS
  • ·One concrete hardening change you would make

Bitcoin’s P2P network is not just plumbing. Peer selection, relay, and topology affect censorship resistance, privacy, and whether your node sees the same chain tip as the honest majority.

Why this matters

Wallets and services that trust a small set of peers inherit those peers’ view of the mempool and chain. Protocol builders who ignore gossip security ship fragile products.

Eclipse and partitions

An eclipse attack aims to surround a victim with attacker-controlled peers so the victim’s view of the network is filtered. Related risks include BGP-level routing interference and intentional network partitions.

Compact blocks

BIP-152 compact blocks reduce bandwidth when relaying new blocks by sending short transaction IDs peers likely already have. This improves propagation; it is not a substitute for validating consensus rules.

Loading diagram…

Honest nodes need diverse peers; compacted relay speeds block gossip.

Operator habits

  • Prefer diversity (ASNs, networks, onion where appropriate)
  • Monitor peer churn and unexpected tip disagreements
  • Separate listening services from keys when possible

Common mistakes

further reading

  • bookMastering Bitcoin

    Ch. 10: The Bitcoin Network

progress // sign in

Reading is public. Sign in to mark lessons complete, sync across devices, and unlock your roadmap.

./sign-in-to-track
prevP2P NetworknextSecurity Models & Light Clients

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.

  • Running a “full node” with one trusted outbound peer forever
  • Assuming private RPC + public P2P needs no hardening
  • Confusing relay policy DoS mitigations with consensus safety