You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just built a new PC and loaded Loki GUI wallet 1.5.4 and connected to a remote node and sync'ed. After it was all updated I closed the wallet and when I logged back in the next day the wallet had to resync from 0. I thought that the wallet had the option to store data to the last sync point. I might have made a mistake on the install but I can't seem to see an option to store or force a sync point.
I did make sure Windows had exemptions for all the storage and write locations that the wallet uses.
I am not sure this is an issue but its something I have not been able to resolve.
The text was updated successfully, but these errors were encountered:
I determined that in 1.5.4 if you create a new wallet it will write the wallet Key files without complaining and store the block status so the next time you open the wallet it will start sync from where you left off last.
However if you restore a wallet from keys you will get a Fail to save file "C:/Users/xxxxx/Documents/Loki/wallets\TestWallet.keys" . The wallet keys file will be created but every time you close the wallet and then open that wallet again it will have to resync from 0.
See image after trying to restore wallet from seed.
I just built a new PC and loaded Loki GUI wallet 1.5.4 and connected to a remote node and sync'ed. After it was all updated I closed the wallet and when I logged back in the next day the wallet had to resync from 0. I thought that the wallet had the option to store data to the last sync point. I might have made a mistake on the install but I can't seem to see an option to store or force a sync point.
I did make sure Windows had exemptions for all the storage and write locations that the wallet uses.
I am not sure this is an issue but its something I have not been able to resolve.
The text was updated successfully, but these errors were encountered: