Bitcoin Forum
December 12, 2024, 08:13:41 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: New Address Already has Transactions??  (Read 515 times)
blanc1664 (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
November 22, 2016, 02:49:41 PM
 #1

I'm using Bitcoin Core version v0.12.1 (64-bit).  When I create a new receiving address and look it up on blockchain.info it shows that transactions already exist with that address.   How is this possible?  Should a brand new address have zero transactions associated with it?


For example, I just created this new address "1NJXy8JSSUYjRp7V83thvUbMG1DBuKA6wc".  When I look it up on blockchain.info we see two transactions.  https://blockchain.info/address/1NJXy8JSSUYjRp7V83thvUbMG1DBuKA6wc

What is going on here?   Has my system been compromised, or is this "normal" ?

altcoinhosting
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1006


View Profile
November 22, 2016, 02:51:35 PM
 #2

I'm using Bitcoin Core version v0.12.1 (64-bit).  When I create a new receiving address and look it up on blockchain.info it shows that transactions already exist with that address.   How is this possible?  Should a brand new address have zero transactions associated with it?


For example, I just created this new address "1NJXy8JSSUYjRp7V83thvUbMG1DBuKA6wc".  When I look it up on blockchain.info we see two transactions.  https://blockchain.info/address/1NJXy8JSSUYjRp7V83thvUbMG1DBuKA6wc

What is going on here?   Has my system been compromised, or is this "normal" ?



no, it's not normal... 0.12.1 wasn't deterministic AFAIK, so it should generate new private keys at random. It should not be possible to have 1 collision, let alone multiple. If you were running 0.13.x, and generated a new wallet, it would have been deterministic (HD) if everything was left default. In that case, if your new wallet contained the same seed as somebody else's, you would create exactly the same private keys. The chances of this happening are close to 0, but still a lot larger than creating random keys and hitting existing ones each time.

Are you sure you're not using an old wallet.dat and you're seeing your own transactions? Did you already try to rescan? Are you fully synced?

blanc1664 (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
November 22, 2016, 03:26:09 PM
 #3

I created a few new sending addresses and they all had two transactions when I looked them up on blockchain.info.  

I was fully synced.  

Upon further inspection it looks like the unknown addresses were created when I sent btc to someone.  I was not aware of the sending address (from me), and it didn't show up in my list of receiving addresses.  When I created a new receiving address it used one of my unknown sending addresses.   *relief*   I've been upgrading versions over the years, so these strangely behaving addresses could have been created on a number of versions in the past.

I just upgraded to 0.13.1 and new receiving addresses are all clean.  
calkob
Hero Member
*****
Offline Offline

Activity: 1106
Merit: 521


View Profile
November 22, 2016, 05:14:41 PM
 #4

Its more likely that you are missing something that you have done than it is you have had a key collision.   Undecided
DannyHamilton
Legendary
*
Offline Offline

Activity: 3514
Merit: 4894



View Profile
November 22, 2016, 10:54:59 PM
 #5

- snip -
one of my unknown sending addresses.   *relief*   I've been upgrading versions over the years, so these strangely behaving addresses could have been created on a number of versions in the past.

I just upgraded to 0.13.1 and new receiving addresses are all clean.  

If this issue is resolved, then it would be a good idea to lock this thread (click the link at the very bottom of the thread on the left)
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!