--- title: ERC-4337 Progress report #3 --- # 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](https://www.candidewallet.com/) 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](https://coda.io/@candide/contributors/progress-0-22), follow them on [Twitter](https://twitter.com/candidewallet), read their ERC-4337 posts on [Medium](https://medium.com/@candidelabs/account-abstraction-potential-with-erc-4337-6bf6bf8ab0bf) or join their [Discord](https://discord.com/invite/NM5HakA9nC) server. Happy to see the ERC getting more projects and looking forward to installing the application from the app store. **2. Some breaking API changes for the upcoming second revision of the ERC-4337 specification** * We are adding support for alternative CREATE2 factories and other deployers to our EntryPoint implementation.<br> In the original implementation of the EntryPoint contract, the CREATE2 Factory address is a constructor parameter and it is impossible to change it later on. However, it is critical for us that users of the ERC-4337 can get the same Wallet addresses across all chains, and EntryPoints may need to support different CREATE2 Factories on various networks.<br> You can see the code diff here: https://github.com/eth-infinitism/account-abstraction/pull/100 * We are combining the `paymaster` and `paymasterData` values into a single field<br> This allows us to save some space in the UserOp structure. It is also preventing the UserOpearations from passing a filled `paymasterData` without defining a `paymaster` address which would cause an error. <br>The diff can be seen here: https://github.com/eth-infinitism/account-abstraction/pull/108 * We have relaxed the requirement for the Paymaster's `validatePaymasterUserOp` enabling it to be a non-view method<br> In order to support Paymasters making state changes during the UserOp validation, we have changed the `validatePaymasterUserOp` method to be defined as a non-view method. The standard Bundler should still check that storage-related opcodes are not present in the Paymaster, however, future Bundlers may allow some Paymasters to make state changes. <br>The diff can be seen here: https://github.com/eth-infinitism/account-abstraction/pull/107 * All signature aggregation-related changes have been merged to the `develop` branch A full explanation of our approach to the signature aggregation with ERC-4337 can be found in the previous progress report here: https://hackmd.io/TOLeQMiTSe6yl_8m_xIXTQ **3. A sample "Bundler Server" and "ERC4337 Provider" are ready for public testing** In order to make your first transaction via the ERC-4337, you would normally need a wallet application or browser extension and an RPC endpoint that both support `eth_sendUserOperation`. While there are projects that try to do both, as of now it is almost impossible to send a UserOperation on any network. However, we believe it is important to start testing the protocol during its development. So we have created the following packages: * Single UserOp Flashbots Protect Bundler It is a very minimal Bundler as it only creates bundles with a single UserOperation. This process accepts 'eth_sendUserOperation' calls and turns them into signed transaction calls on EntryPoint. Sending these transactions through the Flashbots Protect API guarantees that only UserOperations that do pay for gas are mined. While more expensive to use and fully centralized, from the Dapps' point of view, this Bundler should be equivalent to the real one. Critically, such Bundler Server can be run locally, allowing you to test your projects without running an entire Nethermind node. * ERC-4337 Provider and Signer for Ethers.js As there are no wallet extensions supporting `eth_sendUserOperation` method and all that it implies, it was impossible to send a UserOperation from the browser and see how your Dapp behaves with it. With ERC-4337 Provider you can wrap an injected Ethereum provider such as MetaMask and it will handle the ERC-4337 stuff internally. Note that it uses a "signed message" to sign on the UserOperation and deploys a very simple Smart Contract Wallet for you. * A sample React-based ERC-4337 web application Combining an ERC-4337 Provider and a Bundler Server you can build ERC-4337 Dapps already today. You don't need to worry about upcoming changes to the ERC-4337 itself or have to implement production-ready ERC-4337 infrastructure. The source code for these packages can be found here: https://github.com/eth-infinitism/bundler We will soon publish the Bundler Server to the NPM and DockerHub and update this post with the links. This is a very early stage for the project so all help and feedback are very much appreciated. Updated on 25-AUG-2022: **4. Progress report by the Proof Of Soud Protocol** The Proof Of Soud Protocol Team has been making steady progress designing and implementing ERC-4337 Smart Contract Wallet with Social Recovery, as well as Paymasters for gas abstraction. You can read the team's [full progress report here](https://docs.google.com/document/d/10JIe6Apirs8KdHGGtFIvs_IFNxLgFNLxOMLynKVgFcY/edit#heading=h.tat6al5f0tw).
Last changed by  
 
ERC-4337 Development Blog
1292

Read more

Bundler Compatibility Test Suite Announcement

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.

12/27/2022
ERC-4337 Progress report #0

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

8/22/2022
ERC-4337 Progress report #2

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!

8/8/2022
ERC-4337 Progress report #1

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.

7/22/2022
Read more from ERC-4337 Development Blog
Published on HackMD