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
There is a new and growing web3connect login library in the works: https://github.com/web3connect/web3connect
It is an npm package that allows developers to choose from many different web3 login options like MetaMask, Portis, Fortmatic, etc.
It would be great if we could also give the user the option to generate a burner in localstorage and use it as their web3 provider. So they would have all the login options like Portis but could also just hit “Generate Burner” or something.
Scope
Create a web3 provider using something like Metamask’s web3-provider-engine or Frame’s eth-provider that acts like the Burner. It should store the PK in localstorage and sign transactions etc…
Bounty
There is a new and growing web3connect login library in the works:
https://github.com/web3connect/web3connect
It is an npm package that allows developers to choose from many different web3 login options like MetaMask, Portis, Fortmatic, etc.
It would be great if we could also give the user the option to generate a burner in localstorage and use it as their web3 provider. So they would have all the login options like Portis but could also just hit “Generate Burner” or something.
Scope
Create a web3 provider using something like Metamask’s web3-provider-engine or Frame’s eth-provider that acts like the Burner. It should store the PK in localstorage and sign transactions etc…
This would probably be built using the burner-core library: https://github.com/austintgriffith/burner-core
@dmihal might be a good person to look at this first or help someone build
Deliverables
Deliver the burner web3 provider to @pedrouid so we can implement it in web3connect
Roles
bounty gardener: name / 10% - 30%
bounty worker: name / 50% - 80%
bounty reviewer: name / 10% - 30%
The text was updated successfully, but these errors were encountered: