Replies: 2 comments 2 replies
-
Maybe some proxy around |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi @Arch0125. We are thinking of ways to support eth_requestAccounts from within a snap, but we are also working on an Accounts API which will likely solve the issue you are referring to. We plan to launch it in MetaMask Flask in a couple months. Please keep an eye on our SIPs repo for more news on this: https://github.com/metamask/sips |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@GuillaumeRx @Montoya
Expected Workflow of the Account Abstraction snap :
Assumptions : The pvt key is derived using the snap and signatures are not manually done by the EOA
-> User clicks on "Connect with MetaMask" button
-> Extension overrides and listens to 'eth_requestAccounts' rpc call and prompts user to use a AA wallet or not
-> If yes snap derives the pvt key/generates one and creates a AA wallet and connects to the dapp
The problem arises here is that theres no connector for the SCW account similar to what we have EOA here
-> Using the interceptor i could only return the address of SCW account to the provider through the interceptor but can't send transactions since its not actually "connected"
So, is there a module/sdk which can be used to connect the account with dapp ?
Beta Was this translation helpful? Give feedback.
All reactions