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 Portis as means to sign transactions instead of Metamask #360

Open
javier-tarazaga opened this issue Jan 21, 2019 · 0 comments
Open
Labels
feature-request New feature or request

Comments

@javier-tarazaga
Copy link
Contributor

javier-tarazaga commented Jan 21, 2019

Summary

A little bit of context of what Portis is:

The Portis SDK allows DApp users to sign transactions and messages inside their browsers without installing anything. Thanks to its end-to-end encryption they maintain absolute control over their private keys while allowing them to easily access the same account and interact with DApps from all of their devices, using a familiar email and password.

In this case, we could expand the range of options our users can use to interact with public chains apart that Metamask.

Motivation

Metamask is fairly simple to use if you know that you actually need it. In case a user sees a DApp for the first time, will not even know what Metasmask is. In this case we can offer a few options to sign transactions in case other of our users rather prefer using a different provider than simply use Metamask.

Documentation

You can find more information here:
https://developers.portis.io

@filippsen filippsen added the feature-request New feature or request label Jan 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants