166
TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« on: July 18, 2019, 03:38:47 PM »
Can you try it all over again, and see what the total lag is? Also could you check the log and see what the timestamp difference is and how long it took to recover?
This way we can modify the code to remove that situation.
Also, you didn't explain if it was a locked wallet; was it because the wallet was locked and then you unlocked it and the problem goes away after a certain amount of time? (The error in the log would be telling).
I wonder if we should design the wallet to be able to mine without being unlocked. Maybe this is a hurdle for newbies.
Again, is this 1.4.5.9 that is being tested (cause I think 1.2 in prod was a few months ago).
I am on 1.4.5.9 against mainnet
The wallet was locked but I unlocked and this message was there for several hours after unlocking.
However I repeated the same steps now and I can't reproduce the same message, it behaves as normal.
So maybe it was a glitch on my end.
About unlocking the wallet, I think it would be user friendly to detect that user has setgenerate=true and then, if wallet is locked, show some red message on the Overview screen to unlock it.