Ethereum Protocol Fellowship - The Third Cohort (Update 10)

This is the tenth update for Ethereum Protocol Fellowship - The Third Cohort.

In the past two weeks, I finished implementing sanity checks of user operations when the bundler received them and prepared the environment for running bundler spec tests.

Updates

  1. Sanity checks of user operations merged: https://github.com/Vid201/aa-bundler/pull/24
  2. Prepare docker files for running bundler spec tests: https://github.com/Vid201/aa-bundler/pull/52
  3. Chain id is retrieved from the execution client: https://github.com/Vid201/aa-bundler/pull/56
  4. RPC endpoint eth_getChainId: https://github.com/Vid201/aa-bundler/pull/56
  5. RPC endpoints eth_supportedEntryPoints and eth_estimateUserOperationGas: https://github.com/Vid201/aa-bundler/pull/59
  6. Fix bug when calling function simulateValidation on entry point smart contract: https://github.com/Vid201/aa-bundler/pull/61

This was the week I first started checking and running the bundler spec tests. As expected, only the tests for some RPC endpoints passed, and others failed. The goal for the coming weeks is to pass tests now that the environment is set up gradually.

Bundler spec tests

Next steps

There is only one week left in the fellowship; how time flies! My goal is to fix some of the current minor bugs in the repo (CI caching, estimate user operation gas …) and then work on opcode banning and simulation of user operations to pass some more tests until ETH Denver. I will also work on the presentation and final document for the fellowship.

Since I will not finish the bundler in one week, I will continue working on it open-source after the fellowship.

Last changed by 
 
Vid201
0
341

Read more

ERC-4337 Account Abstraction - Silius (bundler implementation in Rust)

The following document provides architecture, design, and specifications for the ERC-4337 (Account Abstraction - AA) Bundler implementation in Rust. This project was started in the Ethereum Protocol Fellowship - The Third Cohort but is still being actively developed.

Mar 27, 2024
Account abstraction - Ethereum Slovenia Meetup (Feb 2024)

asdfasdf

Jan 29, 2024
Demystifying ZKML

As you may have already known, one of the technologies that is getting the most recognityion in the Web3 space are zero knowledge proofs (ZKPs). This is of course understanable, since the technology can serve as foundation for scalbaility of the blockchain - especially Ethereum. But using ZKP can actually enable two features: succints proofs of computation and privacy. And there several different areas they can b used to enhance things, such as for decentralized identity (Polygon ID), private transacttions (Aztec Network), and what this bloog post is about - machine learning (or artificial intelligence if we want to stick to the buzzwords).

Nov 27, 2023
Ethereum Protocol Fellowship - The Third Cohort (Final Update)

All good things come to an end. This is the final update for Ethereum Protocol Fellowship - The Third Cohort. It's a little bit longer, but there are many things to be said. Project summary The project's core goal was to dive deeply into the world of account abstraction and EIP-4337 by implementing some sort of node-equivalent component called bundler in the programming language Rust. The main jobs of the bundlers are accepting user operations (which are similar to transactions) that come from smart contract wallets, bundling them together into bundles, and submitting bundlers to EL (execution layer) clients as standard transactions. Here is the list of some of the most critical things bundlers must perform (to work correctly and be safe from different attacks, such as DOS): When user operation is received, it is validated (so-called sanity checks), e.g., property sender is a contract or initCode is not empty. User operations are also simulated on-chain, and the simulation function must always revert. Simulation is executed by calling a specific smart contract function through the debug_traceCall endpoint, and opcodes are verified; e.g., some opcodes that can change when a user operation is actually submitted to the chain are forbidden. The whole model of EIP-4337 contains several entities, such as senders/accounts, paymasters, factories, and aggregators. To prevent malicious behavior, all the entities have on-chain/off-chain reputations, influencing the actions allowed for entities.

Feb 25, 2023
Read more from Vid201
Published on HackMD