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

Add support for Portis #900

Open
sohkai opened this issue Aug 1, 2019 · 1 comment

Comments

@sohkai
Copy link
Member

commented Aug 1, 2019

See Portis and its UX guidelines.

Portis is essentially a centralized custodian of your Ethereum account, that makes it easy for you to sign up and recover keys via email.


Technically it is not difficult to integrate, but it does require some changes to how we currently handle providers.

Our current strategy:

  1. Check if a local web3 provider is installed (e.g. MetaMask, Frame extension, etc.), use it if so
  2. Fallback to connecting to Frame through eth-provider

With Portis, we would need to introduce a new step, likely at the beginning, that asks the user what signing provider they'd like to use. We could save this information locally, so the next the user loads, they would automatically use the same provider as last time (but ideally have a way to switch providers if desired).

@bpierre

This comment has been minimized.

Copy link
Member

commented Aug 1, 2019

With Portis, we would need to introduce a new step, likely at the beginning, that asks the user what signing provider they'd like to use.

This could also be a improvement compared to the current mechanism, e.g. when a user has Metamask installed but explicitly wants to connect to Frame or another provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.