{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "bitcoin-address-reuse",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/bitcoin-address-reuse/",
  "collection": "bitcoin",
  "title": "Bitcoin address reuse: what it reveals",
  "description": "See what repeated use of a Bitcoin address reveals and why fresh addresses improve separation without making the transaction graph anonymous.",
  "aliases": [],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T18:15:23.891Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "bitcoin-address-reuse-quick-answer",
    "sourceIds": [
      "bitcoin-dev-wallets",
      "bitcoin-whitepaper"
    ]
  },
  "keyFacts": [
    {
      "label": "Visibility",
      "value": "Repeated receipts to the same destination are visible in the ledger.",
      "sourceIds": [
        "bitcoin-dev-wallets"
      ],
      "id": "visibility",
      "claimId": "bitcoin-address-reuse-fact-visibility"
    },
    {
      "label": "Derivation",
      "value": "An HD wallet can derive many receiving keys from its hierarchy.",
      "sourceIds": [
        "bip32"
      ],
      "id": "derivation",
      "claimId": "bitcoin-address-reuse-fact-derivation"
    },
    {
      "label": "Limits",
      "value": "Combining inputs can create additional relationships between receipts.",
      "sourceIds": [
        "bitcoin-whitepaper"
      ],
      "id": "limits",
      "claimId": "bitcoin-address-reuse-fact-limits"
    }
  ],
  "prerequisites": [
    "is-bitcoin-anonymous"
  ],
  "sections": [
    {
      "id": "example",
      "heading": "Separate receipts that would otherwise share a label",
      "sourceIds": [
        "bitcoin-dev-wallets"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "change",
      "heading": "Receiving addresses are only part of the picture",
      "sourceIds": [
        "bitcoin-dev-wallets",
        "bitcoin-whitepaper"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "public-key",
      "heading": "An extended key changes the observer’s view",
      "sourceIds": [
        "bip32"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does a new receiving address mean I need a new seed backup?",
      "answer": "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.",
      "sourceIds": [
        "bip32",
        "bip39"
      ]
    }
  ],
  "claims": [
    {
      "id": "bitcoin-address-reuse-quick-answer",
      "articleSlug": "bitcoin-address-reuse",
      "statement": "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.",
      "sourceIds": [
        "source-38ff15e10892f1ee",
        "source-0e46aca4dbc5a030"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-38ff15e10892f1ee",
          "locator": "Wallet Programs; Public Key Distribution-Only Wallets; Hierarchical Deterministic Key Creation"
        },
        {
          "sourceId": "source-0e46aca4dbc5a030",
          "locator": "Sections 4–5 and 7–11"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Checked BIP-32 public derivation, developer-guide distribution wallets and white-paper section 10. Fresh destinations reduce address-level linking but later multi-input spends and exported xpubs reveal relationships.",
          "Privacy claims are narrowed to observed activity and do not convert clustering into proof of a named owner."
        ]
      }
    },
    {
      "id": "bitcoin-address-reuse-fact-visibility",
      "articleSlug": "bitcoin-address-reuse",
      "statement": "Visibility: Repeated receipts to the same destination are visible in the ledger.",
      "sourceIds": [
        "source-38ff15e10892f1ee"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-38ff15e10892f1ee",
          "locator": "Wallet Programs; Public Key Distribution-Only Wallets; Hierarchical Deterministic Key Creation"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Checked BIP-32 public derivation, developer-guide distribution wallets and white-paper section 10. Fresh destinations reduce address-level linking but later multi-input spends and exported xpubs reveal relationships.",
          "Privacy claims are narrowed to observed activity and do not convert clustering into proof of a named owner."
        ]
      }
    },
    {
      "id": "bitcoin-address-reuse-fact-derivation",
      "articleSlug": "bitcoin-address-reuse",
      "statement": "Derivation: An HD wallet can derive many receiving keys from its hierarchy.",
      "sourceIds": [
        "source-225ce32b9f96878c"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-225ce32b9f96878c",
          "locator": "Extended keys; Child key derivation; Security"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Checked BIP-32 public derivation, developer-guide distribution wallets and white-paper section 10. Fresh destinations reduce address-level linking but later multi-input spends and exported xpubs reveal relationships.",
          "Privacy claims are narrowed to observed activity and do not convert clustering into proof of a named owner."
        ]
      }
    },
    {
      "id": "bitcoin-address-reuse-fact-limits",
      "articleSlug": "bitcoin-address-reuse",
      "statement": "Limits: Combining inputs can create additional relationships between receipts.",
      "sourceIds": [
        "source-0e46aca4dbc5a030"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-0e46aca4dbc5a030",
          "locator": "Sections 4–5 and 7–11"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Checked BIP-32 public derivation, developer-guide distribution wallets and white-paper section 10. Fresh destinations reduce address-level linking but later multi-input spends and exported xpubs reveal relationships.",
          "Privacy claims are narrowed to observed activity and do not convert clustering into proof of a named owner."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "bitcoin-dev-wallets",
      "label": "Bitcoin Developer Guide: Wallets",
      "publisher": "Bitcoin developer documentation contributors",
      "url": "https://developer.bitcoin.org/devguide/wallets.html",
      "locator": "Wallet Programs; Public Key Distribution-Only Wallets; Hierarchical Deterministic Key Creation",
      "note": "Spending keys, address derivation, backups and privacy trade-offs.",
      "version": null,
      "checkedAt": "2026-10-02T17:03:41.163Z",
      "contentSha256": "e136c099f4abfa15673e3ead4f06e61536de38a71b88ef4a8965706c718d5893",
      "recordId": "source-38ff15e10892f1ee"
    },
    {
      "id": "bitcoin-whitepaper",
      "label": "Bitcoin: A Peer-to-Peer Electronic Cash System",
      "publisher": "Satoshi Nakamoto",
      "url": "https://bitcoin.org/bitcoin.pdf",
      "locator": "Sections 4–5 and 7–11",
      "note": "Most-work chain selection, Merkle inclusion, SPV limits and transaction change.",
      "version": "2008 paper",
      "checkedAt": "2026-10-02T17:03:41.335Z",
      "contentSha256": "b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553",
      "recordId": "source-0e46aca4dbc5a030"
    },
    {
      "id": "bip32",
      "label": "Hierarchical Deterministic Wallets",
      "publisher": "Bitcoin BIPs contributors",
      "url": "https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki",
      "locator": "Extended keys; Child key derivation; Security",
      "note": "Extended public keys, derivation and private-key exposure limitations.",
      "version": "BIP-32; immutable revision pinned in source URL",
      "checkedAt": "2026-10-02T17:22:20.467Z",
      "contentSha256": "e5e00a8289db2f681052cf24a745320afc225e66b25d1e489a7c884d2fc7f11f",
      "recordId": "source-225ce32b9f96878c"
    },
    {
      "id": "bip39",
      "label": "Mnemonic code for generating deterministic keys",
      "publisher": "Bitcoin BIPs contributors",
      "url": "https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0039.mediawiki",
      "locator": "From mnemonic to seed",
      "note": "The optional passphrase participates in deriving a different seed.",
      "version": "BIP-39; immutable revision pinned in source URL",
      "checkedAt": "2026-10-02T17:22:20.588Z",
      "contentSha256": "afcbcbed36fe9eb734bd607398a8c124683ded2a75c3830e1b16c47b043a9134",
      "recordId": "source-a7583e32275982ab"
    }
  ],
  "related": {
    "articles": [
      "bitcoin-coin-control",
      "bitcoin-change-addresses",
      "bitcoin-extended-public-keys"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "Initial Bitcoin encyclopedia entry at this permanent URL."
    },
    {
      "date": "2026-10-02",
      "kind": "publishing-format",
      "summary": "Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification."
    }
  ],
  "citation": "Degrees 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/"
}