Allow removing/expiring or firewalling bitcoin addresses #8338

issue RHavar opened this issue on July 13, 2016
  1. RHavar commented at 4:52 PM on July 13, 2016: contributor

    Having un-needed bitcoin addresses presents a privacy problem in bitcoin core's wallet, because they can be sprinkled with (possibly dust) amounts of money, and when that money gets (automatically) spent, it provides lots a lot of extra information that can be used to cluster/analyze the wallet.

    Bitcoin services that need extra privacy (and use bitcoin core) tend to get around this by periodically rebuilding an entire new wallet (which is a pain in the ass). My preferred solution to the problem would be a simple: bitcoin-cli removeaddress $addr which could both tackle the privacy problem as well as wallet bloating over time

  2. laanwj added the label Wallet on Jul 14, 2016
  3. laanwj commented at 10:59 AM on July 14, 2016: member

    There has been much previous discussion on this topic, for anyone starting on an implementation I'd suggest reading these first:

    • #1653 Ability to freeze / erase private keys
    • #3314 Exposed / Compromised (must sweep) / Used / Imported (?) flags on addresses
    • #8338 Ability to hide/delete receive addressess
    • #5525 Add removeaddress RPC call (remove watch-only address)
  4. laanwj cross-referenced this on Aug 10, 2016 from issue Add deleteprivkey and forgetaddress RPC calls by maaku
  5. RHavar closed this on May 3, 2017
  6. bitcoin locked this on Sep 8, 2021
Contributors
RHavarlaanwj
Labels
Wallet
Linked (view graph)
#1653 Ability to freeze / erase private keys#3314 Exposed / Compromised (must sweep) / Used / Imported (?) flags on addresses#5525 Add removeaddress RPC call (remove watch-only address)#8488 Add deleteprivkey and forgetaddress RPC calls
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-20 06:55 UTC