You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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:
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
The text was updated successfully, but these errors were encountered: