Open ritave opened 2 years ago
@chaitanyapotti
At present, this would probably be implemented by means of a wallet_invokeSnap
called within MetaMask itself. Here are some quick thoughts about how this could be implemented:
implementedServices
, or requestedServices
. If the service secretImports
is specified in the manifest, the snap will be expected to implement the RPC method and we will display the requisite UI in MetaMask.
secretImports
service be a permission? Conceptually, the ability to import secrets is not necessarily a permission because the snap is not being granted a new authority. The snap can already receive information from the outside world, and it is already receiving information from the host.Hey team! Please add your planning poker estimate with ZenHub @FrederikBolding @Mrtenz @GuillaumeRx @hmalik88 @eriknson
I may lack some context here, how is this useful as an API to expose to snaps? What's the use case? 🤔
This will be possible with the Snap Keyring Accounts API
@yashovardhan @chaitanyapotti We've been designing a new API that allows snaps to manage accounts in MetaMask. It's possible to import private keys using that APIs. If you would like to shape how the APIs looks so that it can be useful for your case. Now's a good time get involved in discussions
MyEtherWallet would like to import private keys to Metamask and let them show up as an another account in MetaMask.
Key management snaps should be able to import private keys in a secure way.
This is dependent on Keyrings and Blockkit like UI.