New receiving addresses in bitcoin core show old addresses

[helloeverybody]

Hi,

Ive got a small problem that whenever i make a new receiving address to send to someone to receive payment it doesnt create a clean address, What i mean by this is i can see old transactions from other addresses when i put the new address into block explorer. Is this supposed to happen? I thought the whole point of making new addresses every time was for more anonymity which i dont seem to be getting.

so is this normal? i thought not.

thanks

[1715162860]

1715162860

[1715162860]

1715162860

[1715162860]

1715162860

[1715162860]

1715162860

[DannyHamilton]

Hi,

Ive got a small problem that whenever i make a new receiving address to send to someone to receive payment it doesnt create a clean address, What i mean by this is i can see old transactions from other addresses when i put the new address into block explorer. Is this supposed to happen? I thought the whole point of making new addresses every time was for more anonymity which i dont seem to be getting.

so is this normal? i thought not.

thanks

Which wallet are you using?
What version of that wallet are you using?
Are you certain you don't have any malware running on your computer?
What method or process are you using to "make a new receiving address"?

[helloeverybody]

Hi,

Ive got a small problem that whenever i make a new receiving address to send to someone to receive payment it doesnt create a clean address, What i mean by this is i can see old transactions from other addresses when i put the new address into block explorer. Is this supposed to happen? I thought the whole point of making new addresses every time was for more anonymity which i dont seem to be getting.

so is this normal? i thought not.

thanks

Which wallet are you using?
What version of that wallet are you using?
Are you certain you don't have any malware running on your computer?
What method or process are you using to "make a new receiving address"?

Hi,

Its bitcoin core wallet
version v0.11.2 (32-bit)
I may have malware but dont think so
the method im using is i go to file then receiving address, when the new window opens i press new which then creates a new address. I can show you an address if it helps any.

thanks

[cr1776]

Hi,

Ive got a small problem that whenever i make a new receiving address to send to someone to receive payment it doesnt create a clean address, What i mean by this is i can see old transactions from other addresses when i put the new address into block explorer. Is this supposed to happen? I thought the whole point of making new addresses every time was for more anonymity which i dont seem to be getting.

so is this normal? i thought not.

thanks

Which wallet are you using?
What version of that wallet are you using?
Are you certain you don't have any malware running on your computer?
What method or process are you using to "make a new receiving address"?

Hi,

Its bitcoin core wallet
version v0.11.2 (32-bit)
I may have malware but dont think so
the method im using is i go to file then receiving address, when the new window opens i press new which then creates a new address. I can show you an address if it helps any.

thanks

It probably would be helpful to see what you are talking about.

Are you sure you are just seeing transactions that funded the address that is paying you?

[helloeverybody]

Hi,

Ive got a small problem that whenever i make a new receiving address to send to someone to receive payment it doesnt create a clean address, What i mean by this is i can see old transactions from other addresses when i put the new address into block explorer. Is this supposed to happen? I thought the whole point of making new addresses every time was for more anonymity which i dont seem to be getting.

so is this normal? i thought not.

thanks

Which wallet are you using?
What version of that wallet are you using?
Are you certain you don't have any malware running on your computer?
What method or process are you using to "make a new receiving address"?

Hi,

Its bitcoin core wallet
version v0.11.2 (32-bit)
I may have malware but dont think so
the method im using is i go to file then receiving address, when the new window opens i press new which then creates a new address. I can show you an address if it helps any.

thanks

It probably would be helpful to see what you are talking about.

Are you sure you are just seeing transactions that funded the address that is paying you?

Ok this address is a new receiving address 1Nm5NNUsZ9NDZrgLazS5bVpobx3rmEiUch, as you can see there have been transactions that can be traced back, I thought when i create a new address it should look like this 12bMxrSjoTfygNjC1GKp5r7PeXwkSkEBRE. Every new address i make link back to my other addresses for some reason or is that completely normal?

[achow101]

Ok this address is a new receiving address 1Nm5NNUsZ9NDZrgLazS5bVpobx3rmEiUch, as you can see there have been transactions that can be traced back, I thought when i create a new address it should look like this 12bMxrSjoTfygNjC1GKp5r7PeXwkSkEBRE. Every new address i make link back to my other addresses for some reason or is that completely normal?

That is strange. It is most likely that these are change addresses that your wallet already used. It shouldn't be giving you change addresses.

I think this may have to do with an empty keypool (I need to look this up though). It may be possible that the keypool is empty because you have used many new addresses but have not unlocked the wallet in order to allow the keypool to refill so it resorts to giving you change addresses.

Can you provide the debug.log file?

[dserrano5]

I think this may have to do with an empty keypool (I need to look this up though). It may be possible that the keypool is empty because you have used many new addresses but have not unlocked the wallet in order to allow the keypool to refill so it resorts to giving you change addresses.

Some time ago I ran into this. BC refused to give me a new address, I had to unlock the wallet in order to progress.

[DannyHamilton]

Have you recently recovered a backup of your wallet?  I suppose it could be possible that after replacing a newer wallet.dat with an older one the software might have failed to rescan the blockchain and therefore not realize that it previously used these addresses?  If so, then a re-scan might fix the problem.

Otherwise, as knightdk and dserrano5 have pointed out, it's possible that you have used the entire keypool since the last time you entered your password.  Have you not entered your password into the wallet in a long time?

[helloeverybody]

Ok this address is a new receiving address 1Nm5NNUsZ9NDZrgLazS5bVpobx3rmEiUch, as you can see there have been transactions that can be traced back, I thought when i create a new address it should look like this 12bMxrSjoTfygNjC1GKp5r7PeXwkSkEBRE. Every new address i make link back to my other addresses for some reason or is that completely normal?

That is strange. It is most likely that these are change addresses that your wallet already used. It shouldn't be giving you change addresses.

I think this may have to do with an empty keypool (I need to look this up though). It may be possible that the keypool is empty because you have used many new addresses but have not unlocked the wallet in order to allow the keypool to refill so it resorts to giving you change addresses.

Can you provide the debug.log file?

I was thinking it might be change addresses i will try unlocking the wallet and then trying again and see what happens if not i will try re indexing as danny says. I think i did recover this wallet a few months ago and i wouldnt have even noticed that it was giving me dodge addresses, Its just by chance that i checked on in block explorer yesterday .

Since you mention the debug log im getting a lot of this if it means anything to you.

Code:

2016-07-13 16:01:35 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:01:59 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:02:01 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:02:19 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:02:31 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:02:41 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:02:59 ERROR: AcceptToMemoryPool: inputs already spent
2016-07-13 16:03:26 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:04:12 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:04:22 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:04:23 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:04:35 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:05:22 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:06:15 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:06:43 GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.
2016-07-13 16:07:12 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:07:23 keypool reserve 15
2016-07-13 16:07:24 keypool keep 15
2016-07-13 16:07:26 GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.
2016-07-13 16:07:46 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:07:50 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:08:05 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:08:12 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:08:14 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:08:47 GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.
2016-07-13 16:09:09 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:10:05 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:10:19 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:10:39 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:10:58 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:11:01 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:12:00 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:12:26 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:12:53 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:13:08 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:13:50 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:14:49 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2016-07-13 16:14:51 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:15:47 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2016-07-13 16:16:25 ERROR: AcceptToMemoryPool: nonstandard transaction: dust

Edit:- unlocking didnt do the job. looks like a reindex

Have you recently recovered a backup of your wallet?  I suppose it could be possible that after replacing a newer wallet.dat with an older one the software might have failed to rescan the blockchain and therefore not realize that it previously used these addresses?  If so, then a re-scan might fix the problem.

Otherwise, as knightdk and dserrano5 have pointed out, it's possible that you have used the entire keypool since the last time you entered your password.  Have you not entered your password into the wallet in a long time?

It has been ages since i unlocked it but still have the same problem so will have to try the reindex.

[achow101]

I was thinking it might be change addresses i will try unlocking the wallet and then trying again and see what happens if not i will try re indexing as danny says. I think i did recover this wallet a few months ago and i wouldnt have even noticed that it was giving me dodge addresses, Its just by chance that i checked on in block explorer yesterday .

Rescan, not reindex. There is a difference. Reindexing is not going to help.

Since you mention the debug log im getting a lot of this if it means anything to you.

Those errors are useless. It just means you need to upgrade   The latest version doesn't have those errors look so scary.

Code:

2016-07-13 16:07:23 keypool reserve 15
2016-07-13 16:07:24 keypool keep 15

These two lines though show that your keypool has keys left.

[helloeverybody]

Sorry to sound like a total newb but whats the command for rescan? I tried -rescan but its not found and when i googled it it says that -rescan is no longer needed because it checks automatically so i must be doing something wrong.

edity:-i get method not found when i try -rescan code -32601

[achow101]

Sorry to sound like a total newb but whats the command for rescan? I tried -rescan but its not found and when i googled it it says that -rescan is no longer needed because it checks automatically so i must be doing something wrong.

edity:-i get method not found when i try -rescan

You do the same thing for reindexing. You have to start Bitcoin Core with the -rescan option. The instructions depend on your OS.

[helloeverybody]

Sorry to sound like a total newb but whats the command for rescan? I tried -rescan but its not found and when i googled it it says that -rescan is no longer needed because it checks automatically so i must be doing something wrong.

edity:-i get method not found when i try -rescan

You do the same thing for reindexing. You have to start Bitcoin Core with the -rescan option. The instructions depend on your OS.

Ok thanks for everyones help, Its been ages since ive touched much in core but ive got it rescanning now (had to make a new shortcut) but hopefully this will fix it, if not i can use old addresses i generated months ago if i desperately need them for anything. I know its not a major problem so i will live with it if not =p

Edit:- rescan is complete but ive still got the same problem so i will just live with it for now.

[Abdussamad]

you should upgrade to the latest stable version of bitcoin core. 0.11 is old. whatever bug you are encountering may have been fixed in newer versions of the program.

[helloeverybody]

you should upgrade to the latest stable version of bitcoin core. 0.11 is old. whatever bug you are encountering may have been fixed in newer versions of the program.

It might be an idea just to upgrade anyways i suppose and then hopefully in doing so it will sort this problem as well.  Worth a shot.