Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Utilization in Chrome Extensions #319

Open
curldapps opened this issue Oct 2, 2019 · 1 comment
Open

Utilization in Chrome Extensions #319

curldapps opened this issue Oct 2, 2019 · 1 comment

Comments

@curldapps
Copy link

Hi MetaMask team -

Thanks for providing this awesome provider engine! I wanted to get your opinion/pointers on using this provider engine inside my own Chrome Extension. Could I use this to inject web3 into web pages in the context of a custom Chrome Extension?

Essentially, I need a way to format and sign Ethereum transactions from a custom Chrome Extension, and I am exploring options to do this without requiring end-users to install multiple different extensions.

The user would need to be able to create a key, then create a transaction, and sign it for submission which requires injected web3 and a provider. Any guidance on viability and integration of this engine into a custom extension would be hugely appreciated.

Thanks

@curldapps
Copy link
Author

A potential workaround (non-ideal) is that users are required to have MetaMask installed as well and use the provider therein to do the transaction processing:

https://medium.com/@writeprovidence/how-to-create-a-web3-provider-from-another-extension-6b5ea59ed4c9

In an ideal world, I would like to be able to generate a key and process the transaction within one single extension.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant