EIP-4337 Account Abstraction & Smart Contract Wallets featuring Stackup
HTML-код
- Опубликовано: 1 окт 2024
- Learn about Ethereum account abstraction, smart contract wallets and EIP-4337 with code examples from Stackup.
Vitalik Buterin blog post:
/ erc-4337-account-abstr...
EIP-4337:
eips.ethereum....
Stackup wallet:
www.stackup.sh/
Stackup GitHub:
github.com/sta...
Stackup Dischord:
/ discord
![Cody Johnson - I'm Gonna Love You (with Carrie Underwood) [Official Music Video]](http://i.ytimg.com/vi/yy9PuYMU29g/mqdefault.jpg)
I understand nothing, i speak French...small English, it's possible, but technically 🤷... but i follow you 👍practice makes perfect 🥰
Please make axie infinity clone 🤙🚀🔥
Which part in the architecture supports multisig wallets and private key replacements?
this was really helpful. Thanks you :)
Missed you man! .. thanks for the vid
Do stackup use Layer 2 chains ??? like zk synk or rollups? Because using ethereum L1 chain may increase the gas fee , if opted for L2 we may avoid useroperation mempool , Bundler ,Handleops
yes, it's on Polygon...great point
Nice explanation, finally AA is fitting in my brain. I was looking to implement a spend limiter using ERC 4337 on any EVM chain (Polygon for example). Could you point me to wards any resources which I should refer to, or in general help out in what needs to be done to implement a feature like that?.
Thank You
What if the chain that we have is an L1-EVM, but is gasless already? Would our wallet still work?
188
super helpful video!
Is that the correct Discord channel?
The link has been updated - please try again.
Can you explain how private keys tie into 4337 wallets? Is the idea that someone / some company has private keys and these alone are used to create the smart contract wallets for all users?
Furthermore, can you explain how user signatures are created for user operations if they don't have access to the private keys?
Great question. No company or central authority would have access to the private key(s) - the keypair would be generated in the dApp client with any cryptographic library such as ethers Wallet API. The wallet smart contract would then verify signatures and UOs. Hope that helps.
@@BlockExplorerMedia - thanks for your reply!
1. keypair generation via ethers wallet api makes sense to me
2. is it on the user to store that somewhere since they'll have to create signatures for their UOs?
3. what happens if the user creates a eip4337 wallet A with keypair A and then later loses keypair A... is wallet A access gone forever or would the owner of the smart contract factory be able to swap to a new keypair B (in this case, stackup can swap the keypair out?)
Yes, basically it is up to the user or the dApp can manage the private keys and abstract that from the user, via usual password entry. This part isn't much different from other EOAs. In terms of losing the private key - there is something called 'guardians' where you can designate other accounts to act as a 'guardian' of your own account and they would have the ability to generate a new keypair on your behalf in the event of you losing your key. This functionality is specific to smart contract wallets, as far as I know.
Curious about Account Abstraction? Portkey's AA wallet simplifies your Web3 journey. It allows you to sign up with your Web2 details, granting access to decentralized identities and assets. It's all about making Web3 more accessible and user-friendly.
can you help me?, all my usdt tied to the smart contract has been stolen, can it be stolen back?
It was stolen from your Stackup wallet?