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
This issue applies to wallets created by scanning a single OTP code. Double OTP wallets are not affected.
The client mistakenly creates the wallet expecting two OTPs to be used, even if the user did not tick "use second code to enhance security". As a result, the user never got a chance to scan the second OTP, but the wallet is generated in a way such that it is only usable with two OTPs. Therefore, the user would never be able to spend or recover funds in the wallet.
I have upgraded the client to version 0.8.1 (https://github.com/polymorpher/one-wallet/tree/v0.8.1). The problem no longer exists. I have added warning messages in the UI to alert users not to use the wallet if its version is 8.0.
The problem can be prevented with more thorough end-to-end testing. Since the issue was at the client side, the automated testing at core and smart contract levels are not sufficient. More automated tests should be added to the client as well.
REMEDY:
If your wallet is created with a recovery address, simply recover the funds by going to "Recovery" tab and click "Recover".
If your wallet is created without a recovery address and you have funds in that wallet, please reply below or contact me
The text was updated successfully, but these errors were encountered:
This issue applies to wallets created by scanning a single OTP code. Double OTP wallets are not affected.
The client mistakenly creates the wallet expecting two OTPs to be used, even if the user did not tick "use second code to enhance security". As a result, the user never got a chance to scan the second OTP, but the wallet is generated in a way such that it is only usable with two OTPs. Therefore, the user would never be able to spend or recover funds in the wallet.
I have upgraded the client to version 0.8.1 (https://github.com/polymorpher/one-wallet/tree/v0.8.1). The problem no longer exists. I have added warning messages in the UI to alert users not to use the wallet if its version is 8.0.
The problem can be prevented with more thorough end-to-end testing. Since the issue was at the client side, the automated testing at core and smart contract levels are not sufficient. More automated tests should be added to the client as well.
REMEDY:
If your wallet is created with a recovery address, simply recover the funds by going to "Recovery" tab and click "Recover".
If your wallet is created without a recovery address and you have funds in that wallet, please reply below or contact me
The text was updated successfully, but these errors were encountered: