fether issueshttps://gitlab.parity.io/parity/fether/-/issues2018-07-02T12:07:31Zhttps://gitlab.parity.io/parity/fether/-/issues/5The Signer2018-07-02T12:07:31ZGhost UserThe Signer@brianflanagan Something that we didn't discuss yet: the signer part. Basically each account can be unlocked by one of the following methods:
- password
- QR code on mobile phone
- hardware wallet (like nano S)
- a private key JSON f...@brianflanagan Something that we didn't discuss yet: the signer part. Basically each account can be unlocked by one of the following methods:
- password
- QR code on mobile phone
- hardware wallet (like nano S)
- a private key JSON file
Obviously for v1 we will only implement the password unlocking, but it would be good to keep in mind that we will extend that in the future. The question is: when should the user unlock his account?
The UX MetaMask has is one password for all accounts, unlocked at the very beginning. This would not work with us because some accounts are password-protected, while (in the future) other accounts can be unlocked differently (which MM doesn't offer). Moreover, I won't store the password anywhere, which is a security +.
I'd suggest prompting the user to input his password only when needed, i.e. when confirming sending the transaction.
The - is that if the user has 6 accounts, he'd need to remember 6 passwords.https://gitlab.parity.io/parity/fether/-/issues/4Follow transaction after sending it2018-07-02T12:07:31ZGhost UserFollow transaction after sending itAfter submitting a transaction, the transaction isn't immediately confirmed, there are several steps, described [here](https://wiki.parity.io/oo7-Parity-Reference#transactionstatus) in TransactionStatus. And after the `confirmed` step ab...After submitting a transaction, the transaction isn't immediately confirmed, there are several steps, described [here](https://wiki.parity.io/oo7-Parity-Reference#transactionstatus) in TransactionStatus. And after the `confirmed` step above, we still wait for 6 confirmations (cf bottom right corner of this screenshot https://user-images.githubusercontent.com/11201122/39359080-2c0f8896-4a21-11e8-9f8b-2af11cc7fa6a.png)
This process can take 1-2 minutes. During all this time I believe the user should be able to keep an eye the status of his transaction, while doing other stuff on the UI.
Note: there can be multiple transactions at the same time, but that's P2 priority.