Hello everyone in the ERC-4337 community! 2022 has been a great year for Account Abstraction. We have come a long way, from an early idea to multiple implementations from different teams, with numerous established companies as well as new startups betting on ERC-4337 becoming the next big thing for Ethereum! We are happy to announce that the latest revision of ERC-4337, as well as the EntryPoint implementation, has reached "release candidate" status and will be in code freeze, pending results of a scheduled security audit. You can read the full release notes of this version here: https://github.com/eth-infinitism/account-abstraction/releases/tag/v0.4.0 MAJOR ANNOUNCEMENT! We strongly believe the best way to achieve the goals of ERC-4337 is through a unified network of bundlers and clients. This is why we are also announcing the Bundler Compatibility Test Suite: https://github.com/eth-infinitism/bundler-spec-tests . This set of tests verifies that different Bundlers are able to communicate properly and defend themselves against DoS attack vectors. The tests verify that compliant Bundlers propagate only valid UserOperations through the mempool, handle signature aggregation correctly, prevent UserOperations from accessing restricted storage slots and opcodes, etc. Non-compliant Bundlers are at risk of being attacked and losing money. We encourage all Bundlers to pass all tests in order to defend themselves against DoS attacks and to remain compatible with the mempool shared by all other ERC-4337 Bundlers. Our team will maintain a list of compatible Bundler implementations and our website will provide links to all the compatible bundlers that pass the tests. The reference implementation of the Bundler that is compliant with the Test Suite has already been finalized and has been published to Dockerhub. This Bundler is not intended for use in production, but rather as a reference to other bundler implementations. You can read the full release notes of this version here: https://github.com/eth-infinitism/bundler/releases/tag/v0.4.0 Thanks to everyone who has been contributing to the ERC-4337 related projects for your great work this year. We are looking forward to continuing the collaboration with all the great projects in the Account Abstraction space and hope to have even more of your feedback and input going forward.

ERC-4337 Progress report #3 Monday, August 22, 2022 Hello everyone! A little late with the report this week, however, there is some really good news that I am glad to share. 1. First, welcome Candide Wallet to the ERC-4337 club! They are developing a mobile-first wallet application with ERC-4337 support with Dart and Flutter. You can read their own progress report, follow them on Twitter, read their ERC-4337 posts on Medium or join their Discord server.

ERC-4337 Progress report #0 Thursday, July 7, 2022 Hello everyone. We are glad to see work on the ERC-4337 accelerating and also to see new people joining in every day! Trying to keep everyone in the loop, we will post a bi-weekly progress report for all projects in the ERC-4337 family. For the first progress report I will just list the projects and components that were created in relation to the ERC-4337 that I am aware of. Please DM me if I have missed anything and I will add it to the document. UserOp Block Builder Bundler

ERC-4337 Progress report #2 Thursday, August 4th, 2022 Hello everyone. Over the last two weeks, we have focused on tweaking some changes we are making to the ERC-4337 based on some feedback we have got from the community. However, there are still some great news to celebrate: Stackup, the ERC-4337 powered wallet, has launched. You are invited to congratulate the team and read their announcement on Product Hunt. Good luck!

ERC-4337 Progress report #1 Thursday, July 21, 2022 Hello everyone. It has been two weeks since the previous post, and we are glad to announce a major improvement to the ERC-4337 that will be crucial for adoption of Account Abstraction, especially for Layer 2 networks: adding support for Aggregated Signatures. The core benefit of signature aggregation is that instead of passing and verifying a signature for each individual UserOperation in a bunde, we only need to pass a single signature that verifies the entire bundle of UserOperations. If this verification passes, it means that all signatures in a batch were in fact valid, and if there was a single invalid signature in a batch the aggregated signature verification will fail as well. This way we save a lot of crucial calldata size, which is the major part of trasnaction cost for L2 networks. Signature aggregation promises a great savings in both calldata and, eventually, execution gas, and going from "Account Abstraction gives you more flexibility but costs a little bit more gas" to "Account Abstraction gives you more flexibility AND saves you gas" will help us eventually overtake the EOAs.