Observed since 20 Oct, 20:01 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
Account Abstraction Snap
|
|
|
|
|
DApps want to add Account Abstraction support but the problem is that every dApp might end up using its own Account Factory leading to different counterfactual address for Smart Contract Wallet
Users will end up having different SCW for every dApp which leads to complex UX
The AA snap will basically offload all the work the frontend devs need to do to add AA support to their dApps, instead the Metamask Snap will use a single Account Factory (so single CounterFactual address) and the dApp developers need not change anything they can keep on request signing transactions as usual!
No Contracts are to be deployed, the Smart Contract Wallets are deployed using Thirdweb Account Factory and Pimlico.
git clone https://github.com/therealharpaljadeja/aa-snap.git
yarn start
The above will open up the site at localhost 8081 port
Any Transaction UI, you will need to specify to address and calldata which is the simple calldata used in the Ethereum txs.TOKEN_CONTRACT value inside chains object in /packages/site/pages/index.tsx file (make sure to do it under the right chain)I am using Infura's Linea testnet RPC here, here and here to query the blockchain and make read calls, basically when creating Keyring accounts I need to read from the Entrypoint the counterfactual address of the Smart Contract Wallet which will in-turn be deployed on first transaction!
eth_sendTransaction if that can be done, its endgame!Download counts and popularity will appear here as the collector receives them.
This describes our collected data; it is not a security assessment.
Shared repository data · GitHub
Observed since 20 Oct, 20:01 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
package:6a1d302e1e2d8c58b5802c581242774e5c508ffb8a0a73071f1c2f94e1632143