mimblewimble
inconsistent wallet transactions state
Is your feature request related to a problem? Please describe. After a long reorg that doesn't mine any transactions (double-spend...) which has been received and directly spent during the reorg, these transactions are in inconsistent state. We don't check whether they are still confirmed or not, eg we don't track the kernel. That's a big issue for wallets handling a lot of transactions volume.
Describe the solution you'd like If a reorg is detected and our latest block scan is included in the stale blocks, check the kernel of the confirmed received/spent transactions and change their status to unconfirmed if they were not mined again at the end of the reorg.
I think that's something that we might want to address, otherwise the only option is a scan from scratch which might lose any local data that is kept.
