Instant Send lock information is not broadcasted when wallet starts
Motivation
When performing an instant send transaction a lock request is broadcasted through the network. All locked transactions are kept in scope of applications global variable and when application restarts it doesn't have any information about locked transactions in network.
Side effects
- After receiving some amount of crown via instant send it is possible to spend it after one confirmation. But after rebooting the wallet it will not allow to spend the received coins because wallet doesn't have any information of that transaction being locked.
- GUI shows (5 of 6 confirmations) immediately after receiving instant transaction. But after reboot it shows the actual amount of confirmations.
- Proposal created by instant send is shown right after creation but disappears when rebooting the wallet. It appears again after 6 real confirmations.
There can be others
Suggestion
Request information about locked transaction from the network when starting wallet like it is done in case of systemnode list, masternode list, proposals etc.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information