What's New in Account Abstraction? | Dror Tirosh - ERC-4337

now uh hello everyone my name is dy Ros I'm on the ERC 4337 coure team and I'm here to talk about what's new with ERC 437 with a c obstruction and uh what we've accomplished uh in the in the past year and moving forward so exactly one year ago here in Denver uh we announced on stage the main release of ESC 4427 we just passed the security audit pass then uh since then uh if we look what happens in then so we can see in traffic uh we see that now we reached some the vicinity of 2 million transaction or user operation uh per month we've reached over 700 100 monthly users using account abstraction which I believe it's quite good for the first year uh we've seen a lot of H activity with the our partners on the network we have a like great uh slideshow we've seen a a lot of activity we like we've seen 27 wallets and sdks active open source bundlers that you can download and use our own reference bundler and many others and multiple service bundler a service and pay Master a service available on the blockchain Block explorers a lot of uh traffic done there there ER we also released many grants many of those DEC and bundlers and the block Explorer received grants for for doing things around account obstruction ESC 437 doing different signature schemes metric dashboards accounts Etc uh very interesting is to see that this is the the ACT Gas pay by pay masters we see that 95% of all user operations of all transaction were sponsored which means that the idea of having a sponsor pay Master uh really kicks in users like the idea of using a simpler servers than using a native tokens for paying gas and pay Master play a great deal doing that these are several of the eaps that yes sorry ercs and eips that surrounded the account obstruction we have modular wallets led by Alchemy and by rhinestone pushing stand modular accounts standards uh 6900 and 7579 uh using a popular signature scheme that available on each phone pass keys and wean uh with which is a EAP 7 to 12 and uh you see 64 92 for allowing a signing uh transaction even sorry signing messages even before your account exist this is something that basically missing from a contract accounts now accounts just like on par with the EAS can perform signatures uh pushing forwards we are working uh very hard with our partners to having the mol the P2P menol several bundlers already supported uh with the previous release that we released a year ago which called entry point 0.6 uh 0.7 which was just released uh we'll move forward and we stay tuned about to release it next month in London about our releases last year we released a version 0.6 and with each version we are trying to make it more secure we all everything about decentralized uh accounts and uh so the entry point has to make sure the network is secured so version .6 was all about making transaction and hashes available to All Tools around them version 7 again pushed the simulation and uh the security of pay masters and uh also uh you move a one step forward towards a native account obstruction which will see shortly now if we try to look what we are pushing the the way forward the way we see it there's we have a the protocol front the puzzle there is the ESC 4337 itself which becomes more mature with version .

7 we just passed the security audit and we extracted the core validation rules the complex part that Define how the mpol is kept decentralized and secure into a separate ERC and we started to work on the the native account obstruction LC 7560 and make sure that ER it is aligned with the 4357 more about it later uh on the networking front we are contined the work in the maintenance of our reference bundler and mol as we seen and trying to push a different chain to adapt the network it is more than just running a bundler on a network uh in parallel we are working on implementing uh a GU guas Fork to support the native account obstruction this is still not available there is no chance that currently use it h but all the work that we have done both in bundlers and accounts and pay masters will be a will work towards both the ERC 4337 and the native account obstruction on the account front we've seen a lot of work as I said by Alchemy pushing 6900 for modular count obstruction and another standard for modular count obstruction 7569 uh we we try to help them moving forward and the various specific ercs we've seen earlier to support those accounts on the pay masters all of the pay Master we've seen most of the pay Master we've seen earlier Are all uh pay master that work within offchain signatures what we call verifying pay Master which actually it's a way that the pay Master takes a user confirmation to pay offchain and makes this validation onchain we are moving forward to push a to improve the standard to to have better support for token pay masters which are completely onchain decentralized to allow you use tokens I want to uh stress more about I mentioned several times the the native account obstruction first of all Native account obstruction we call it an RP which is a it's not an EAP it's a rollup Improvement protocol we understand that native account obstruction is something that will start with a h side chains actually innovation in general start with more with side chain and uh with the understanding that mainnet will be is less Innovative and less uh and more secure the idea is to push a new features into a rollups first so we started an initiative we called RP which is rollup first and actually AP 70 to2 for a supporting pys is past SN R which means it is not something that is expected in the near future on mainnet but it surely will be accepted first on H rollups and uh side chains ER we also push the native account obstruction as a rollup as as an RP to be accepted by rollups now what is uh RP uh 7560 in short short it is a enshrined version ESC 4337 it is built from grounds up in order to be interoperable with the force with7 if we think why we are trying to push it because we already seeing that several l2s are pushing their own versions ofc 437 like Stark neck and Z casing they they are built on the architecture of 4367 but each one of them made some modification this modification make them incompatible with the 4337 which means it's going to be very difficult for a wallet to support both standards with this understanding that we need something that is compatible that to allow account modular accounts to support both native and ERC 4337 uh we started to work on 7560 and as I said it's not something that we think think we go to main it soon we want to we want to see it on L tools first what does it give uh of us first of all as I say it is compatible with 437 in that it's going to be quite easy for our account to support both it has lower gas fees it reduces the overhead of having the entry point as a contract because it becomes part of the protocol uh it support uh in the long term it will support migration from o this is something that is very much anticipated everybody ask us how can we use ESC 437 weas and the answer of course is right now it is impossible but with the 7560 it will be eventually possible to migrate your account uh it supports some security features like inclusion list and uh and almost most importantly it means there is a network commitment there's a network that accept a a native account abstraction means that uh it expects you can expect the network to support it if there is a problem like there is in the network you do expect if needed the the the network to do what it need to save the user funds if there is a problem in the accounts themselves um I moved a bit fast so um anyone has any questions okay thank you