Update - 6

Hello everyone, I wanted to give you all an update on the progress I've been making with our chrome extension and the development of smart contract wallets (SCWs). In this update, I'm excited to share that I've successfully been able to inject a Web3Provider into the current tab using the content script of our chrome extension.

One of the areas I've been focusing on is adding multiple chain support for our SCWs. After some research, I've determined that the keyring controller will still be active on a single chain, and whenever we change the chain in the App, we'll be creating a new different instance of the keyring controller for that specific chain.

As that I was researching multi-chain support, I came across the issue of how to have the same address across multiple chains, and the challenges around managing changing of ownership across multiple chains. To address this, I've been exploring the use of EigenLayer. I've even written a blog post on this topic, which you can check out at https://mirror.xyz/plusminushalf.eth/hIrS59bVgHhnSCC9B9rp7XnGT-PBOCWPponWwEzKjsE. In this post, I'm exploring the idea of a separate chain for wallets to mitigate the account management problem.