Bitcoin-qt sends change back to used address

[romerun]

I was on an impression that reusing addresses is not a good practice, but I also noticed that the classic client sometimes picks old addresses to receive changes, isn't it a bad thing?

[DannyHamilton]

I was on an impression that reusing addresses is not a good practice, but I also noticed that the classic client sometimes picks old addresses to receive changes, isn't it a bad thing?

I think it only does this in situations where you've recovered an old backup, right?

Regardless, I agree that re-using previously used addresses for change should be considered to be a bug, and should be fixed in the next release if possible.  Has this been reported yet?

[romerun]

Ah, that explains it. I set the keypool to a big number and made backups of it. I always delete my wallet after done sending, and start over with one of the backups on the next time of use.

Has this been reported yet?

Nope.

[Foxpup]

I always delete my wallet after done sending, and start over with one of the backups on the next time of use.

Why the Hell would you do that? What made you think that was a good idea?

[romerun]

To prove that my backups are as good as wallet.dat, well actually it's for security reasons, I don't like leaving wallet.dat on the common place as I encrypted the backups so many times and spread them on cross locations and it will be a painful process to update all of them every time I send anything.

[romerun]

just reported it here

https://github.com/bitcoin/bitcoin/issues/4192