Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate Parity Signer #1056

Closed
maciejhirsz opened this issue Feb 12, 2018 · 4 comments · Fixed by #1349
Closed

Integrate Parity Signer #1056

maciejhirsz opened this issue Feb 12, 2018 · 4 comments · Fixed by #1349
Assignees
Labels
type: feature Items that are larger in scope and are classified as a new feature (as opposed to an enhancement)

Comments

@maciejhirsz
Copy link
Contributor

maciejhirsz commented Feb 12, 2018

Disclaimer

This is kind of an extension of: MyEtherWallet/etherwallet#551

Also I'm actually happy to sit down and implement it myself, but I'd like to hear if it's something you'd be willing to include in the first place.

Description of the Feature

Parity has developed a Parity Signer mobile app a while ago, it's available both on iOS and Android. The app can be a low entry barrier alternative to hardware wallets (especially if you have an old phone that you can turn completely offline and run the app on it).

The app in combination with the Parity client UI allows you to store the private key on your phone, recover wallet from Parity phrases (which solves the MEW issue linked above for us), and sign transactions done in the browser via QR codes - the raw transaction is presented as a QR code, scanned by the app, signed in the app, and then a QR code with the signed transaction can be scanned by the browser via webcam.

I reckon it should be reasonably easy to port the QR scanning code to MyCrypto, which would offer the users a more secure way of handling their private keys than using keystore files / phrases in the browser directly. It can also help with phishing since the app displays the transaction details from the QR code to the user (how much ether and to whom is going to be transferred, regardless of what the web UI displays).

Yay/nay?

@dternyak
Copy link
Contributor

dternyak commented Feb 12, 2018

Thanks for opening this issue @maciejhirsz!

A big yay from me.

We've brainstormed a similar proposal that you can find at #921, however these are distinct enough that they will need to be implemented independently.

I would certainly be in favor of merging a PR if you do submit one that includes your described functionality.

Let me know if there's anything further I can help with, and feel free to ask any questions you might have while getting acclimated to the codebase here.

Edit: Happy to invite you to our internal slack as well if you want to talk out the design there :)

@5chdn
Copy link

5chdn commented Feb 13, 2018

Btw, the signer apps are open-source if you have use for them https://github.com/paritytech/parity-signer

@maciejhirsz
Copy link
Contributor Author

@dternyak sure, slack me up - maciej@parity.io. I'll start working on this as soon as I'm done with some other more pressing issues. My general idea is to make a React component library for that, to make the integration easier (plus there might be other projects that could benefit from it).

@dternyak
Copy link
Contributor

@maciejhirsz Done! I like the idea of making a general purpose react component library to more fully modularize the implementation.

@wbobeirne wbobeirne added type: feature Items that are larger in scope and are classified as a new feature (as opposed to an enhancement) XL labels Mar 6, 2018
@maciejhirsz maciejhirsz mentioned this issue Mar 20, 2018
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature Items that are larger in scope and are classified as a new feature (as opposed to an enhancement)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants