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?

imo it would make sense to have a core config that is synced across chains and where modules are tied to some identifies (eg address, ens, ...) and then a way to override this config on different chains. what is tricky is that modules themselves have configs so this also needs to be synced