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.

Sign up for GitHub

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

Jump to bottom

Consider allowing Snaps to have more direct access to Metamask Infura infrastructure #400

Open
ritave opened this issue Apr 25, 2022 · 0 comments
Open

Consider allowing Snaps to have more direct access to Metamask Infura infrastructure #400

ritave opened this issue Apr 25, 2022 · 0 comments
Labels
area-capabilities Related to the kinds of things that snaps are able to do. type-enhancement New feature or request type-research A research task.

Comments

@ritave
Copy link
Member

ritave commented Apr 25, 2022

Currently if Snaps want to support custom networks, they have to go out of band and use their own infrastructure to communicate with the network such as their own Infura keys. Having custom Infura keys in a public Snap is not the greatest idea. We could somehow allow Snaps to get access to Metamask's network infrastructure to be able to connect to IPFS, Polygon, Eth2, etc using Metamask provider.

CC @jeffprestes
@ritave ritave changed the title Consider allowing Snaps to have more direct access to Metamask infura infrastucture Consider allowing Snaps to have more direct access to Metamask Infura infrastructure Apr 25, 2022
@rekmarks rekmarks added type-enhancement New feature or request type-research A research task. area-capabilities Related to the kinds of things that snaps are able to do. labels May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-capabilities Related to the kinds of things that snaps are able to do. type-enhancement New feature or request type-research A research task.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ritave @rekmarks