I had previously commented on this.
My references to wallet ver were really to nFileVersion.
And I've since been able to make that, and the
real walletversion become current.
However it is still doing this every invocation...
Rescanning last 14xxx blocks (from block 170xxx)...
Which seems unneede
I think there may be an ideal order of ops bug around rescan,
wallet upgrades/import and last block markers.
I dropped an old wallet in a current blockchain.
First ran - in rescan mode.
It said old walletver.
Then rescanned whole chain.
AddToWallet some blockhash, blocks out of range, invalid/non
2 matches
Mail list logo
