ไม่สามารถเล่นวิดีโอนี้
ขออภัยในความไม่สะดวก
ฝัง
- เผยแพร่เมื่อ 18 ส.ค. 2024
- In this video we define Account Abstraction more concretely and talk about more of its technical benefits. Then we discuss the different proposals for AA (Account Abstraction) and why EIP 4337 is the one we'll be discussing in future videos.
Signup for a free Alchemy account: dashboard.alch...
Get started with an Embedded Accounts: www.alchemy.co...
Account Abstraction Concepts playlist:
• Account Abstraction
Account Abstraction Tutorials playlist:
• Account Abstraction Tu...
Learn more about Account Abstraction - www.alchemy.co...
Signup for a free Alchemy account - dashboard.alch...
0:00 Introduction
1:03 EOAs and Smart Contracts
1:57 Smart Contract Account vs EOA
3:52 Smart Contract Account vs Smart Contract
5:12 Account Abstraction Proposals
5:57 Wrapping Up
Dan, this was a great intro and background concept for account abstraction!
The examples of old vs new were super helpful. Looking forward to your next video to learn more about how to set up better AA-related UX for DeForm customers who are looking to mint onchain rewards for marketing purposes :)
Thanks Albert!! We do plan on doing a series soon where we just build a bunch of cool new projects using AA. Would love to collab with you guys on a video featuring Deform as well :)
This is concise and helpful. Thanks
Glad it was helpful!
Got some questions popping up in my mind:
1) Will I be assigned a unique smart wallet address for every dapp I connect to?
2) Do I still need a key, like an Externally Owned Account or any signer, to interact with these smart wallets?
3) Does my EOA have control over all the individual smart wallets associated with each dapp?
Great questions!
1) This really depends on the way the dapps are setup, ideally we start moving towards a unified model for the account but there's several schools of thought on what this could look like! We plan to make some more video content shortly discussing how the smart account addresses are derived.
2) Yup! The difference, in this case, is that the key will be only for signing the User Operation which will be validated in the smart account, which has flexible validation. For that reason the key is not limited to the cryptography that the ethereum protocol uses for the EOAs. This means we can start to use passkeys for smart accounts. You could also, for example, have a key which is limited by certain parameters (access, permissions, time limits) that could be stored in the users browser and can sign automatically when a user clicks a button. At the end of the day Account Abstraction unlocks flexibility that allows us to program new UX and, as developers, we need to discover what the right experience is for our users, which may be very use-case dependent.
3) Not necessarily, Account Abstraction really provides flexibility in the account. You could control your smart account by 1 key, or many keys with different permissions.
Thanks for the clear answers! Looking forward to learning more in the upcoming video content.
Hi Dan!
Hey I need help with completing my project using Account Kit. Where can I get some help?
Hey there! You can join our discord community here: discord.com/invite/alchemyplatform
By searching you may find someone who has already asked your question, or you can post your own!
Hello @justkaz7104, did you manage to get assistance, with using Account Kit, I am stuck as well, could you help me?
#0xgas #AccountAbstractionSmart contract wallets redefine blockchain with enhanced security and flexibility