Bitcoin Forum
May 24, 2024, 07:02:15 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Reusable Receive Addresses  (Read 1026 times)
jag2k2 (OP)
Member
**
Offline Offline

Activity: 62
Merit: 10


View Profile
May 02, 2013, 06:12:37 PM
 #1

If this is electrum specific behavior then my apologies but the question I think is more general.  I have been in bitcoin for about a month and in that month my wallet has 5 transactions

Receive 3.7 BTC on Address A
Receive 3.3 BTC on Address B
Send 3.25 BTC so the inputs to the transaction were A&B, the outputs were my destination address and the rest to Address C (Change Address?)
Receive 6.3 BTC on Address D
Receive 0.4 BTC on Address E

The way I see it the sum total of my wallet exists in addresses "C", "D", and "E" correct?  What is odd though is that Electrum shows that Address "B" is still a valid receive address but not Address "A".  I would expect neither to be valid receive addresses at this point since they are both inputs to another transaction.

Does that make sense?  I'm trying to wrap my head around what would happen if I sent bitcoins to Address "B" and why its a valid address when "A" isn't.

Thanks

I believe that banking institutions are more dangerous to our liberties than standing armies... The issuing power should be taken from the banks and restored to the people, to whom it properly belongs. - Thomas Jefferson
nybble41
Full Member
***
Offline Offline

Activity: 152
Merit: 100


View Profile
May 02, 2013, 06:32:23 PM
 #2

Receive 3.7 BTC on Address A
Receive 3.3 BTC on Address B
Send 3.25 BTC so the inputs to the transaction were A&B
Why "A&B"? Either A or B would be sufficient by itself, so there is no reason for Electrum to combine them into a single transaction. It probably used the output of the first transaction (address A), sending the remaining ~0.45 to change address C, and left address B alone.

Technically you can still receive BTC on any of your receive addresses, even ones which have already been used as inputs. Some consider it less secure because the full public key is known from the earlier transactions, as opposed to just the hash of the public key which appears in the outputs. Personally I don't think that's worth worrying over.
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!