# Update - 8 Hey everyone, hope you're all doing well! I have an update on the wallet development. Our goal has been redefined and we're now focusing on making the wallet forkable and customizable for SCW with support for custom onboarding and transaction inputs. Our aim is to have the plugin ready by EthDenver. Here's what we have planned so far: - De-prioritize the secure module for a safe execution environment for multiple wallets (Jan 29th) - Finish the onboarding with a custom screen for SCW to take user input (Jan 29th) - Inject the Web3Provider (Feb 4th) - Create a primary transaction confirmation screen that developers can clone and customize (Feb 7th) - Write a Readme for users to clone the repo and develop (Feb 14th) - Clean up any leftover issues (March 1st) - Modified 2fa extension demo (March 1st) We have updated the timeline based on the progress we've made so far: - Inject Web3Provider (Feb 4th) - Transaction screen (Feb 8th) - Readme (Feb 14th) - Define a simpler Paymaster RPC call (Feb 10th) - WalletApi to expose information about the paymaster (Feb 10th) - Settings page to add paymaster, change bundler URL, provider URL, etc. (Feb 18th) - Reload the background script upon chain change (will see if there's time left) Check out the onboarding video and the video for injecting the Web3Provider below: ### Onboarding Video: {%youtube BZU9lWagLtY %} ### Injecting Web3Provider: {%youtube wq9tN0Wy1f4 %} The new repo can be found at the [link](https://github.com/plusminushalf/aa-account-chrome-extension). Let me know your thoughts and feedback!
Last changed by  
 
Garvit Khatri
122

Read more

Transaction Analysis

TLDR; This is a call from SCW, where the SCW does two transactions. The first being approiving the USDC & then second is calling Socket's registery to bridge the token using the function outboundTransferTo. Transaction Flow: User op was forwarded using Stackup bundler Every userOp call starts with EntryPoint - 0x5ff137d4b0fdcd49dca30c7cf57e578a026d2789 Smart Contract wallet address - 0x3a1ee02cf59821e4d8264a6ddfae970a99da25d5 SCW looks like an implementation of https://ethereum-magicians.org/t/erc-6900-modular-smart-contract-accounts-and-plugins/13885/20 This is mostly popularised by zeroDev protocol - https://mirror.xyz/konradkopp.eth/7Q3TrMFgx2VbZRKa7UEaisIMjimpMABiqGYo00T9egA Codebase - https://github.com/zerodevapp/kernel/blob/main/src/Kernel.sol

5/29/2023
Final Update - EPF

Project Summary I initially aimed to develop the proposed 4337 wallet, a browser extension wallet composed of three modules: extension, auth, and recovery. The aim was to support multiple SCW implementations by exposing the API to allow users to select the SCW implementation they prefer. However, the task turned out to be monumental, and some priorities needed to be set for EthDenver. Thus, we realigned our goals and came up with the following: Deprioritize the secure module for safe execution environments for multiple wallets. Finish onboarding with a custom screen for SCW to take user input. Inject the Web3Provider. Create a primary transaction confirmation screen that developers can clone and customize. Write a README for users to clone the repo and develop. Clean up any leftover issues. Modify the 2fa extension demo.

3/23/2023
Ideas 101

This document highlight the list of ideas that are worth exploring for our startup - PROTON Writing style - challenge - poroblem statement people - target ussers outcome - measurable change in people's life Accounts for app chains

3/4/2023
update - 7

I have been continuing to work on my wallet extension and unfortunately, I have encountered a few blockers that I have not yet been able to solve. However, since my last update, I have become more interested in the possibility of using EigenLayer for account abstraction. Before delving into a potential solution, let's first review the current problems facing wallet development: Fragmentation of ownership, especially when funds are not available on a specific chain. The use of the same address across multiple chains, particularly on newer chains like Starknet and Zksync. Difficulty in creating similar features across different chains; for example, it can be challenging to write zk verifiers in Cairo. The significant development effort required for supporting multiple chains. It is important to note that any solution must prioritize

1/23/2023
Read more from Garvit Khatri
Published on HackMD