--- tags: Ethereum Protocol Fellowship --- # EPF Update 8 ## Summary 1. Review [ paymaster and paymasterData in a single field](https://github.com/eth-infinitism/account-abstraction/pull/108/files) 2. Submit [pr](https://github.com/Vid201/aa-bundler/pull/25) on entry point contract interactions 3. Reading articles about ewasm articles 4. Create [a draft integration test](https://github.com/Vid201/aa-bundler/pull/26) 5. Give an advice for [ethers-rs](https://github.com/gakonst/ethers-rs/issues/592#issuecomment-1351679519) to refactor the code for verion 2. ## Entry point contract API When I was exploring the codes generated by the ethers-rs and trying to interact with the contract. I found it extremely difficult to get the revert data by ethers-rs. This is because the middle ware design is so bad that every result instance must inherit(yes. It is more like oop solution) a lot of methods. So the response object is different if you use different middle ware. It is highly not programable. I review the codes in ethers-rs and contact with the team but sadly they admited the incovinience and would fix it in verion 2. So I need to parse some non-standard string to error type and continue. I hope version could come soon. Besides, the problem I met with ethers-rs. I spent most of my time creating integration test function. I successfully create function to compile the abstract account solidity codes and deploy the codes into a test node. ## Reading List 1. [wasm-for-blockchain](https://medium.com/nearprotocol/wasm-for-blockchain-2019-d093bfeb6133) 2. [wasm-on-the-blockchain-the-lesser-evil](https://medium.com/polkadot-network/wasm-on-the-blockchain-the-lesser-evil-da8d7c6ef6bd)