Bitcoin Forum
June 16, 2019, 11:46:03 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Multiple change addresses  (Read 147 times)
Newar
Legendary
*
Offline Offline

Activity: 1358
Merit: 1000


https://gliph.me/hUF


View Profile
November 19, 2017, 09:41:08 AM
 #1

What do you think of multiple change addresses? (Not my idea, Electrum has them) Might help obfuscate some cases. On the other hand, it will create more outputs that might be more costly to spend later?

OTC rating | GPG keyid 1DC91318EE785FDE | Gliph: lightning bicycle tree music | Mycelium, a swift & secure Bitcoin client for Android | LocalBitcoins
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 2212
Merit: 1118

Armory Developer


View Profile
November 19, 2017, 01:14:50 PM
 #2

It can be useful under certain conditions. If your wallet identifies your spending patterns, it could estimate the most appropriate size for change outputs so as to fit your next spend size more appropriately. This requires a bunch of analytics first and isn't exactly a perfect science.

This isn't particularly useful long term however, as what erodes your privacy with regards to change is cross spending them to a given service. While on the blockchain it does not appear that you are a single user spending to a single service (since they should give fresh deposit addresses), anyone with access to that service's log will identify yours coins easily.

Therefor a setup where the user can signify which service he is spending to would allow the wallet to single out utxos already tainted to that service, at the same time quarantining that chain of utxos from other services.


Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!