Bitcoin Forum
May 02, 2024, 05:54:04 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Specifying a change address for a wallet before actually sending from wallet?  (Read 961 times)
Mousepotato (OP)
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000


Seal Cub Clubbing Club


View Profile
March 23, 2015, 08:21:33 PM
 #1

Sorry if this is a n00b question, but does anybody know if it's possible to specify a change address for a wallet without having to actually send something from that wallet first? I looked it over for a quick minute but it wasn't obvious to me, if it's even possible to begin with.

Mousepotato
1714672444
Hero Member
*
Offline Offline

Posts: 1714672444

View Profile Personal Message (Offline)

Ignore
1714672444
Reply with quote  #2

1714672444
Report to moderator
1714672444
Hero Member
*
Offline Offline

Posts: 1714672444

View Profile Personal Message (Offline)

Ignore
1714672444
Reply with quote  #2

1714672444
Report to moderator
1714672444
Hero Member
*
Offline Offline

Posts: 1714672444

View Profile Personal Message (Offline)

Ignore
1714672444
Reply with quote  #2

1714672444
Report to moderator
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714672444
Hero Member
*
Offline Offline

Posts: 1714672444

View Profile Personal Message (Offline)

Ignore
1714672444
Reply with quote  #2

1714672444
Report to moderator
Carlton Banks
Legendary
*
Offline Offline

Activity: 3430
Merit: 3071



View Profile
March 23, 2015, 08:54:35 PM
 #2

You can do that per transaction, but you can't set one address to receive all change to. Maybe the new wallet format will have a sub-pubkeychain for each wallet or something like that, but it seems like you're looking for a feature that people typically would not want.

Vires in numeris
Mousepotato (OP)
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000


Seal Cub Clubbing Club


View Profile
March 23, 2015, 09:11:07 PM
 #3

Yeah, it's not a huge deal. I was just wanting to preemptively set my change address for all the wallets I use in one fell swoop. I guess I can just do it as I actually use the wallets =]

Mousepotato
spin
Sr. Member
****
Offline Offline

Activity: 362
Merit: 261


View Profile
March 24, 2015, 02:07:41 PM
 #4

Constantly using the same change address reduces the privacy of your transactions.  It makes it easier to analyse your transactions and link them together.

If you liked this post buy me a beer.  Beers are quite cheap where I live!
bc1q707guwp9pc73r08jw23lvecpywtazjjk399daa
Mousepotato (OP)
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000


Seal Cub Clubbing Club


View Profile
March 24, 2015, 05:27:45 PM
 #5

Constantly using the same change address reduces the privacy of your transactions.  It makes it easier to analyse your transactions and link them together.

Yeah but then I'd have to eat the Tx fee when I decide to consolidate each one of those change addresses which might hold an amount less than my Tx fee setting. Can I just do a 0-fee consolidation into an address in my own wallet? What are the risks of that? I'm not too concerned about confirmation time since I'd only do this periodically. Sorry for the n00b questions; I'm new to this Armory stuff :]

Mousepotato
spin
Sr. Member
****
Offline Offline

Activity: 362
Merit: 261


View Profile
March 24, 2015, 09:50:15 PM
 #6

Constantly using the same change address reduces the privacy of your transactions.  It makes it easier to analyse your transactions and link them together.

Yeah but then I'd have to eat the Tx fee when I decide to consolidate each one of those change addresses which might hold an amount less than my Tx fee setting. Can I just do a 0-fee consolidation into an address in my own wallet? What are the risks of that? I'm not too concerned about confirmation time since I'd only do this periodically. Sorry for the n00b questions; I'm new to this Armory stuff :]
Why consolidate? There is no need as far as I can tell.  Plus again you are reducing you privacy by doing so.   
The fees get charged per input.  Even if you change are all at the same address they are still each a separate outputs.  When you are using these in a tx they adding bytes to the tx the same as if they were in separate addresses, thus increasing the fee in the same way. 
Bitcoin transactions work on the output of previous tx not really on addresses.

If you liked this post buy me a beer.  Beers are quite cheap where I live!
bc1q707guwp9pc73r08jw23lvecpywtazjjk399daa
picobit
Hero Member
*****
Offline Offline

Activity: 547
Merit: 500


Decor in numeris


View Profile
March 25, 2015, 12:36:27 PM
 #7

Constantly using the same change address reduces the privacy of your transactions.  It makes it easier to analyse your transactions and link them together.

Yeah but then I'd have to eat the Tx fee when I decide to consolidate each one of those change addresses which might hold an amount less than my Tx fee setting. Can I just do a 0-fee consolidation into an address in my own wallet? What are the risks of that? I'm not too concerned about confirmation time since I'd only do this periodically. Sorry for the n00b questions; I'm new to this Armory stuff :]

Reusing the same address will not help.  You will still have multiple inputs in your next output, it will require the same fee regardless of whether these multiple inputs have the same address or different addresses.

Doing a 0-fee transaction to yourself will lock up your coins until it confirms.  If it never confirms, the transaction eventually goes away.  So there is no real risk.  You should, however, be aware that if your transaction is too small then a fee may be required before the network will even consider transporting your transaction.  I think that Armory in that case refuses to send the transaction without a fee.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!