# How to be productive in AA Breakout room Many people showed up to discuss AA & 3074 during the **[Execution Layer Meeting 186 [2024-04-25]](https://www.youtube.com/watch?v=iLnBFPH-1Gc)** thus a breakout room has been decided to further discuss 3074. We propose to prepare the breakout in order to have a productive debate that focus on objective technical points rather than side meta-discussion about governance. It's not that those discussions are forbidden it's simply that a breakout room is not the venue for them. So we'd like to provide this framework, with the goal to produce an efficient debate, that people are free to follow. Preparing the breakroom with keeping in mind **what is this breakroom for?** Have a look at ["The Hard Parts of Open Source" by Evan Czaplicki](https://youtu.be/o_4EX4dPppA?feature=shared&t=2431) where he discusses intent communications in Open Source projects. And with this in mind I invite you to prepare your communications with the following structure : Intent: *e.g understand 3074 `AUTH`* Background: *e.g I am a wallet dev for a software wallet dealing with EOAs and doing XYZ* Question: *e.g How can I implement 3074 `AUTH` with my constraints X, Y* Another upside of the preparing your points is that you can share them at the beginning of the breakout room allowing to cover as many points as possible without having to replay the debate many times. Of course the discussion will be open and you'll be able to reply by raising hand to take the mic. ## What is the breakout room for ? This breakout is to further discuss. The agenda is the following as per https://github.com/ethereum/pm/issues/1032 ### Breakout room Agenda - In-protocol AA roadmap - Account migration - Smart account originated transactions - Relationship with EIP-3074 - EIP-3074 - Reusing existing infrastructure - 3074 in 4337 - smart account code as invokers - [Combining 5806 with 3074](https://gist.github.com/lightclient/0d8d91264e7875cec4341de930d347ad) - Adding flexibility for chain id / nonce in auth msg - Remove completely - Opt-out with value `0` - Propagate `authorized` with `DELEGATECALL`
Last changed by  
 
Nicolas Consigny
228

Read more

77O2 guidelines

Special thanks to Tim Beiko, Yoav Weiss and Lightclient for feedback and review. Abstract EIP 7702 defines a mechanism to add code to an EOA. This proposal allows EOAs, the legacy ethereum accounts, to receive short-term functionality improvements, increasing the usability of applications. This is done by setting a pointer to already deployed code using a new transaction type: 4. This new transaction type introduces an authorization list. Each authorization tuple in the list is defined as [ chain_id, address, nonce, y_parity, r, s ] address is the delegation (already deployed bytecode that'll be used by the EOA)

4/23/2025
Ideas for a Wallet Dashboard

This document outlines suggestions for creating a comprehensive, credibly neutral dashboard for all wallet solutions, à la L2Beat. “The primary challenge is making sure that all these projects are, collectively, building something that feels like one Ethereum ecosystem, and not 138 incompatible fiefdoms.” - [Vitalik Buterin](https://vitalik.eth. Software wallets (EOA), and smart wallets should be all under one dashboard. Hardware wallets should also be included (maybe in a different page as they're not the same) The Challenge of Being a Wallet Wallets are critical infrastructure and often the primary interface users have with the blockchain. For many, the wallet is the blockchain experience. Evaluating wallets can involve ranking them into stages based on specific criteria, similar to how Layer 2 solutions are assessed. I won't propose an implementation nor help with the execution (as I don't think that should be my role and also don't have the bandwith). But I'm happy to help the brainsorming of criteria and open my network of wallet people to make it happen ! Technical Alignment for Wallets

12/5/2024
Read more from Nicolas Consigny
Published on HackMD