BA-10 · LESSON 04

Network privacy

KEY DEFINITIONS

Terms used in this lesson

IP address: Internet Protocol address: a network identifier that can reveal where a connection originated.
ISP: Internet service provider: a network operator that can observe connection metadata even when it cannot read encrypted application content.
DNS: Domain Name System: a naming service Bitcoin can use during peer discovery without trusting it to validate chain data.
xpub: A serialized extended public key containing a public key and chain code for deriving normal public descendants.

IP observation, timing, wallet queries, and address reuse can reveal links even when on-chain structure is careful.

65 min Difficulty 3/5 Not started

VISUAL MODEL

See the whole mechanism before going step by step

Use the diagrams to orient yourself. Then the guided explanation below teaches every part in depth.

4 explanatory views

CONCEPT-SPECIFIC MAP · privacy boundaryObservable evidence creates inferences, not automatic proofSelect any state to inspect its exact role.

RELATIONSHIP MAPCompeting paths and resolution

01
OBSERVABLEAmount, script, timing
Chain and network observers see different subsets of transaction and propagation data.
02
HEURISTICProbabilistic link
Wallet patterns can support a guess but do not prove a real-world identity.
03
RISKNetwork privacy
The Network privacy lesson identifies which evidence or failure is in scope.
04
CONTROLReduce or separate evidence
Address discipline, coin selection, local verification, and routing choices change exposure.
05
RESIDUALExplicit remaining observer
Every mitigation leaves assumptions and observers that must be named honestly.

Rule shown: Privacy improves by reducing linkable evidence and separating observers, while preserving verifiable spending rules.

STAGE 1 OF 5OBSERVABLE: Amount, script, timing

Chain and network observers see different subsets of transaction and propagation data.

Governing relationship: Privacy improves by reducing linkable evidence and separating observers, while preserving verifiable spending rules. Complete path: 1. OBSERVABLE, Amount, script, timing. Chain and network observers see different subsets of transaction and propagation data. 2. HEURISTIC, Probabilistic link. Wallet patterns can support a guess but do not prove a real-world identity. 3. RISK, Network privacy. The Network privacy lesson identifies which evidence or failure is in scope. 4. CONTROL, Reduce or separate evidence. Address discipline, coin selection, local verification, and routing choices change exposure. 5. RESIDUAL, Explicit remaining observer. Every mitigation leaves assumptions and observers that must be named honestly.

1. State transitionWhat exists, what changes, and what results

BEFORE

Wallet A asks one public server about 20 exact addresses. Wallet B connects to its own fully validating node over a private local link.

MECHANISM

Internet providers, Wi-Fi operators, peers, Domain Name System (DNS) resolvers, wallet servers, and global timing observers see different metadata.

AFTER

On-chain address hygiene cannot compensate for a wallet server that sees the entire address set and identity metadata.

Text equivalent: Starting from Wallet A asks one public server about 20 exact addresses. Wallet B connects to its own fully validating node over a private local link. The mechanism begins when Internet providers, Wi-Fi operators, peers, Domain Name System (DNS) resolvers, wallet servers, and global timing observers see different metadata. The resulting lesson is On-chain address hygiene cannot compensate for a wallet server that sees the entire address set and identity metadata.

2. Mechanism pathSelect a stage to inspect its job

STAGE 1 OF 5

Map observers

Internet providers, Wi-Fi operators, peers, Domain Name System (DNS) resolvers, wallet servers, and global timing observers see different metadata.

Complete path: 1. Map observers: Internet providers, Wi-Fi operators, peers, Domain Name System (DNS) resolvers, wallet servers, and global timing observers see different metadata. 2. Separate transaction origin from relay: Bitcoin's diffusion and relay behavior makes first-peer inference probabilistic, not proof, but broad peer coverage improves an observer's guess. 3. Diversify peer connections: Address-manager buckets group stored peer addresses to limit one source's influence. Anchors are remembered peers used across restarts, and feelers are brief test connections to new addresses. These controls and multiple network paths reduce but do not eliminate eclipse risk. 4. Minimize wallet query leakage: Querying a remote server for exact addresses or scripts derived from an extended public key (xpub) exposes wallet structure. Local full-node validation avoids that server dependency. 5. Use privacy networks with limits: Tor or other routing can hide source IP from peers, while entry correlation, misconfiguration, browser identity, or mixed clearnet use can still link activity.

3. Rule and failure boundaryWhat accepts the result and where it can stop

ACCEPTED PATH

The observer map separately assigns address queries, filter downloads, peer timing, and Internet provider connections without converting those observations into identity proof.

CHANGED CONDITION

One address-group eclipse removes peer diversity, and Tor routing cannot erase remote wallet queries, account data, timing, or address reuse.

Important distinction: Using Tor makes a Bitcoin wallet anonymous. Tor hides some network routing information. Wallet queries, cookies, accounts, timing, address reuse, peer behavior, and endpoint compromise remain separate linkages.

Text equivalent: The accepted path is enforced by The observer map separately assigns address queries, filter downloads, peer timing, and Internet provider connections without converting those observations into identity proof. If the required condition changes, One address-group eclipse removes peer diversity, and Tor routing cannot erase remote wallet queries, account data, timing, or address reuse.

Loading lesson visuals...

Learn the idea

Network privacy concerns who can link a transaction or wallet query to an Internet Protocol (IP) address and time. A first-spy observer guesses that an early announcing peer originated a transaction. An eclipse attack surrounds a node with attacker-controlled peers. Light-wallet address queries can reveal a user's complete interest set even when on-chain addresses are not reused.

GUIDED EXPLANATION1/5 ideas inspected

Map observers

Internet providers, Wi-Fi operators, peers, Domain Name System (DNS) resolvers, wallet servers, and global timing observers see different metadata.

The worked example follows the explanation

Inspect every idea above to open it.

Important distinction“Using Tor makes a Bitcoin wallet anonymous.”

Tor hides some network routing information. Wallet queries, cookies, accounts, timing, address reuse, peer behavior, and endpoint compromise remain separate linkages.

FINISH LEARNING FIRST

The questions unlock after every required learning activity

Inspect every guided idea, open the worked example, rebuild its mechanism, and complete the deterministic lesson tool. Your progress is saved automatically.