fast and decentralized wallet based on a light-client || Download: https://bit.ly/2LcujDj
@joshua-mir I see, thx for the explanation. Still quite confusing at first, but I understand why it developed that way.
Have you considered making that transparent in the UI? I checked on MyCrypto and they are actively discouraging using the parity phrases. If you're generating a new account with fether it might be more consistent with other wallets to use the standard BIP39 phrases. At least it might be useful to mention that to the user. Should I file an issue for that for further discussion?
@chrisdotn the reason MEW/MyCrypto started disallowing the parity phrase for restoration is because people were using it like a brainwallet (manually creating wallets with a phrase they came up with)
Currently parity started giving warnings about using it in that way
Yeah, I understand the reasoning for MyCrypto/MEW. I'm mostly concerned with fether, because it shows a "Restore wallet" option, but doesn't mention that it can only be used with accounts that have been previously generated by parity/fether. It cannot be used with accounts that have been generated by any other tool. At least I fell for that trap because I was used to think that a mnemonic passphrase is universal between different clients. With fether it isn't. So it's just something to consider from the UX side of things
Sorry yeah it's reasonable to put in an issue for that 😅
Hey, I just built the app on Mac OS and the it was just white until I refreshed a number of times. Do you know what the cause might be?
@bemusementpark that's a known issue that you might see if the background parity process isn't running or fether doesn't connect to it properly - are you using your own node or the node provided by fether?
I just ran yarn start
so all defaults (:
I actually ran yarn electron and then yarn start and it went straight to the disclaimer without a white screen.
I’m not sure if that’s just superstion, yeah, it looks like. another white screen.