Ethereum Account Abstraction

AA fam, how are we thinking about the intersection of modules and keystore rollup?

Namely, I assume if a user wants a module on one chain they probably want on all. What’s the best approach?

If modules are deployed to the same addresses across chains, L2 accounts could query the L1 account for approved modules so that they don’t need to be approved on every chain. 

Inspo from https://hackmd.io/@i275DA5ZRjOAeSFUkffw5Q/H1rQQwY9n

@rhinestone team, figure you may have thoughts?

The future of account abstraction is modular

leading Builder Success @base | onchain since '17 | anything for the builders

To have crosschain modules, something about their addresses must be standardized. 

Either they are the same across all chains 
Or
A registry of a module’s crosschain addresses needs to be maintained

Imo it’s easier to simply deploy to the same address on all chains with CREATE2

Yeah but part of the goal of the keystore rollup is giving users a single source of truth signer even when addresses differ. 

I’m not sure modules at the same address should be designed around

yeah I largely agree with this - the ideal solution in my mind would be a central source of truth for account configs and a way to override this for a specific chain