Re: [SSD] Sonic - First coin over TOR with functional anon send - 0% prem
You are full of shit. Try again.
Code:
14:23:30
getnewaddress
14:23:30
scjDCfCAFwhPh5CrrntZM4n2irM3EXmKWp
14:23:32
getnewaddress
14:23:32
seF4pdfCKwH4kppNnJowbuRSh3ZkH34FAX
14:23:36
getnewaddress 'account'
14:23:36
sRFS3cT1qmAYtsVg5miGaQia6skRJjdZA9
14:23:39
getnewaddress 'account2'
14:23:39
saYKAi5SgvwZvWJDSVqavarBpzHs8QwYj5
14:27:13
getnewaddress 'account2'
14:27:13
shFxZ2D7dpULoos2bd9BU7TZ7yUfzLkEV6
getnewaddress
14:23:30
scjDCfCAFwhPh5CrrntZM4n2irM3EXmKWp
14:23:32
getnewaddress
14:23:32
seF4pdfCKwH4kppNnJowbuRSh3ZkH34FAX
14:23:36
getnewaddress 'account'
14:23:36
sRFS3cT1qmAYtsVg5miGaQia6skRJjdZA9
14:23:39
getnewaddress 'account2'
14:23:39
saYKAi5SgvwZvWJDSVqavarBpzHs8QwYj5
14:27:13
getnewaddress 'account2'
14:27:13
shFxZ2D7dpULoos2bd9BU7TZ7yUfzLkEV6
Wallet after migration returned addresses that were used before migration, for example:
sc7zK5PrZUbTTfM2ZKrQ3Q6rnxmLtDr858
scSHt3SGSVFuZP6aBP5UiUzYHfWBy5hu7a
After migration and salvaging wallet, it returned the same addresses, presumably in the same order, my bet that's bug is related to key pool queue, it's developer job to determinate exact cause. If someone has better explanation why it was happened and why addresses were reused, you can post your version of events.
Also if you find a bug feel free to post it, I will gladly admit if I am wrong and fix it.
I think I know what would have happened though.
As you can see in the pastebin the wallet was corrupted and the most recent backup they had was 8 days prior. When reverting to this backup the keypool was taken back to the previous state. This would allow addresses that had already been assigned to be reassigned.