Thank you for this excellent video. It provides a clear and straightforward explanation of the high-level overview of AA. Understanding this concept was a bit challenging for me, but the video made it much easier to grasp!
For both of these questions it can depend on the account the developer sets up. With ERC6900 you can create a modular account installing plugins for increased security (by limiting privileges) and customizable onchain recovery mechanisms, here's a high level overview th-cam.com/video/YHy_d1pvtsw/w-d-xo.html Of course, because these are additional smart contracts on the blockchain, all the contracts should be secure and audited. ERC6900 was built with security in mind. A key feature of this standard are install-time permissions for plugins, as described in that video.
great question - a sequencer, as well as a layer one node, will take transactions and put them on the blockchain. You can think of the bundler as one step removed. It will take user ops, bundle them into a transaction and then submit that transaction to a layer one node, or a sequencer.
Account Abstraction certainly does look complicated! For most devs, a simple solution will provide all of their needs in this department, like our embedded accounts: www.alchemy.com/embedded-accounts At the same time, its helpful to know all the background information to get a feel for what works best with your specific application.
There can be bugs in bundlers, for sure, and the security model is quite tricky! This is just like how there can be bugs in the core clients (like the one recently in Nethermind). One thing to keep in mind though is that a bundler (same as a node) cannot misrepresent your intention as a user. You signed a userOp and it cannot modify that userOp. We use the bundler to get userOps on-chain through a transaction and make gas payment abstraction possible.
![ลองสั่งของจากแอพ temu ถูกจริงหรอ?? ( part : 1/2 ) [โกงไหมครับ ep.89 ] | DOM](http://i.ytimg.com/vi/RTcZSQTiDZw/mqdefault.jpg)
Thank you, that is the most understandable explanation of eip4337 on TH-cam❤
Awesome glad you enjoyed it!
Godly video, especially because of the walkthrough on how you use the tracer tool and 4byte directory. Thanks so much for the overview Dan!!!
So many great tools now!
Thank you for this excellent video. It provides a clear and straightforward explanation of the high-level overview of AA. Understanding this concept was a bit challenging for me, but the video made it much easier to grasp!
You're very welcome!
this is brilliant thank you
Alchemy being Alchemy again. Great content 🔥
Thank you!!! ❤
Hi Dan!
Can you do a tutorial on how to create the dApp on the first Video?
Quite enlightening! Now I see everything! Hahahahahaha
Thanks for showing us these Analysis Tools.
I wonder what other tools are out there I'm missing out? 😮
Hmmm that sounds like a great video idea!
What are the security risks associated with the abstracted account? What happens if they lose their traditional log in credentials?
For both of these questions it can depend on the account the developer sets up. With ERC6900 you can create a modular account installing plugins for increased security (by limiting privileges) and customizable onchain recovery mechanisms, here's a high level overview th-cam.com/video/YHy_d1pvtsw/w-d-xo.html
Of course, because these are additional smart contracts on the blockchain, all the contracts should be secure and audited. ERC6900 was built with security in mind. A key feature of this standard are install-time permissions for plugins, as described in that video.
How is a bundler different from a sequencer?
great question - a sequencer, as well as a layer one node, will take transactions and put them on the blockchain. You can think of the bundler as one step removed. It will take user ops, bundle them into a transaction and then submit that transaction to a layer one node, or a sequencer.
can I replace the smart contract account with a EOA account in this process
Hi Dan!
Brian!!
As times goes by things on Ethereum starts to look veeery complicated
Account Abstraction certainly does look complicated! For most devs, a simple solution will provide all of their needs in this department, like our embedded accounts: www.alchemy.com/embedded-accounts
At the same time, its helpful to know all the background information to get a feel for what works best with your specific application.
Can bundler be compromized?
There can be bugs in bundlers, for sure, and the security model is quite tricky! This is just like how there can be bugs in the core clients (like the one recently in Nethermind).
One thing to keep in mind though is that a bundler (same as a node) cannot misrepresent your intention as a user. You signed a userOp and it cannot modify that userOp. We use the bundler to get userOps on-chain through a transaction and make gas payment abstraction possible.
1
#1 all day