Encyclopedia How the network works · Entry 91
Bitcoin address reuse: what it reveals
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Visibility | Repeated receipts to the same destination are visible in the ledger. | [1] |
| Derivation | An HD wallet can derive many receiving keys from its hierarchy. | [3] |
| Limits | Combining inputs can create additional relationships between receipts. | [2] |
Separate receipts that would otherwise share a label
A creator who places one permanent donation address on a profile makes all payments to that destination easy to group. Issuing separate addresses for separate invoices removes that simple address-level grouping.
It does not hide the invoices from parties who already received them, and it does not conceal amounts or later spending relationships on the public chain.
Receiving addresses are only part of the picture
Wallets also create change outputs. If several receipts are spent together, their shared transaction can suggest common control. That is a heuristic about a transaction pattern, not proof of a named person.
Coin selection and change handling therefore matter alongside address generation. A privacy claim based only on “a new address every time” leaves out later spending.
An extended key changes the observer’s view
An observer given the relevant extended public key may derive many addresses even when each individual payment uses a fresh destination. The wallet has changed visible addresses without hiding them from that observer.
Use receiving information at the narrowest scope appropriate to the task. A payment address, account descriptor and master-level public export expose different amounts of information.
Direct answers
Questions people ask
Does a new receiving address mean I need a new seed backup?
Not ordinarily for addresses derived within an already backed-up deterministic wallet hierarchy. The backup must still cover the relevant seed, passphrase and derivation information.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Bitcoin address reuse means receiving more than once to the same output destination. It makes those receipts easy to associate and can expose patterns when the outputs are later spent. Fresh addresses reduce this direct link, but public transaction structure and other information can still connect activity.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimVisibility: Repeated receipts to the same destination are visible in the ledger.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimDerivation: An HD wallet can derive many receiving keys from its hierarchy.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimLimits: Combining inputs can create additional relationships between receipts.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimRevision history
- — Initial Bitcoin encyclopedia entry at this permanent URL.
- — Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Bitcoin Developer Guide: WalletsBitcoin developer documentation contributors
Spending keys, address derivation, backups and privacy trade-offs.
Locator: Wallet Programs; Public Key Distribution-Only Wallets; Hierarchical Deterministic Key Creation · Retrieved: 2026-10-02T17:03:41.163ZOpen source - Bitcoin: A Peer-to-Peer Electronic Cash SystemSatoshi Nakamoto
Most-work chain selection, Merkle inclusion, SPV limits and transaction change.
Locator: Sections 4–5 and 7–11 · Version / scope: 2008 paper · Retrieved: 2026-10-02T17:03:41.335ZOpen source - Hierarchical Deterministic WalletsBitcoin BIPs contributors
Extended public keys, derivation and private-key exposure limitations.
Locator: Extended keys; Child key derivation; Security · Version / scope: BIP-32; immutable revision pinned in source URL · Retrieved: 2026-10-02T17:22:20.467ZOpen source - Mnemonic code for generating deterministic keysBitcoin BIPs contributors
The optional passphrase participates in deriving a different seed.
Locator: From mnemonic to seed · Version / scope: BIP-39; immutable revision pinned in source URL · Retrieved: 2026-10-02T17:22:20.588ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Bitcoin address reuse: what it reveals.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-address-reuse/