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
Upon moving from testnet8 to testnet9 I basically assumed that I was supposed to enter the same ./PASSWD value into the "passphrase section", I had no idea at all that:
MMX uses a 25th word, and my putting a new value into the "With Passphrase" section results in you unlocking another wallet.
The "With Passphrase" is different from your ./PASSWD value.
The PASSWD value isn't actually related to your wallet, it's just to stop cross-scripting attacks to the GUI.
I'm supposed to record the 'With Passphrase' value if i set it, and if I don't I'll loose access to my funds.
There definitely needs to be more "idiot-proofing" in the GUI imo... Like I'm really not a novice user and I was bitten by this, I have no doubt if MMX became popular that you would have a LOT of less experienced users running into this same issue.
As we can see here there isn't really any indication that by setting a "passphrase" I'm actually setting the 25th word of my seed and I'll need to hang onto that passphrase to recovery my finds in the future:
The text was updated successfully, but these errors were encountered:
The file name 'PASSWD' likely has something to do with it, it's too similar to "Passphrase", renaming it as 'GUI-LOCK' or something might help avoid this confusion.
I believe I've run into a usability issue.
Upon moving from testnet8 to testnet9 I basically assumed that I was supposed to enter the same ./PASSWD value into the "passphrase section", I had no idea at all that:
There definitely needs to be more "idiot-proofing" in the GUI imo... Like I'm really not a novice user and I was bitten by this, I have no doubt if MMX became popular that you would have a LOT of less experienced users running into this same issue.
As we can see here there isn't really any indication that by setting a "passphrase" I'm actually setting the 25th word of my seed and I'll need to hang onto that passphrase to recovery my finds in the future:
The text was updated successfully, but these errors were encountered: