I very often do fresh syncs with new wallet.dat's and use SilentDragon. This means that senttxstore.dat and addresslabels.dat become out-of-sync and the GUI does really weird stuff, like thinking an address that is not in your wallet is a sprout address, and giving mysterious address validation errors.
We need to better verify that the data in these files makes sense, and if it doesn't, I think the most sane thing is to move the file out of the way and "back it up" for the user, in case they want it.
I very often do fresh syncs with new wallet.dat's and use SilentDragon. This means that senttxstore.dat and addresslabels.dat become out-of-sync and the GUI does really weird stuff, like thinking an address that is not in your wallet is a sprout address, and giving mysterious address validation errors.
We need to better verify that the data in these files makes sense, and if it doesn't, I think the most sane thing is to move the file out of the way and "back it up" for the user, in case they want it.
I very often do fresh syncs with new wallet.dat's and use SilentDragon. This means that senttxstore.dat and addresslabels.dat become out-of-sync and the GUI does really weird stuff, like thinking an address that is not in your wallet is a sprout address, and giving mysterious address validation errors.
We need to better verify that the data in these files makes sense, and if it doesn't, I think the most sane thing is to move the file out of the way and "back it up" for the user, in case they want it.
I am wondering if the above bug relating to showing something as a sprout address still exists, or if that was fixed.