Content
@
https://warpcast.com/~/channel/ethereum-aa
0 reply
0 recast
0 reaction
Wilson Cusack
@wilsoncusack
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?
4 replies
9 recasts
89 reactions
eric.base.eth 🔵
@ericbrown.eth
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?
2 replies
0 recast
1 reaction
conner
@symmetry
Devised a system using an Account Circuit that can process solidity libraries and then use a create2 factory to deploy modules. https://hackmd.io/@ilikesymmetry/solidity-account-circuits
1 reply
0 recast
1 reaction
abstractooor
@konrad
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
0 reply
0 recast
0 reaction
Colin
@obiequiet
If chains are focused on specific types of applications (defi vs gaming chains), some modules might not be desired or useful on both! Recovery keys are a pretty basic case, but modules for session keys and subscriptions you'd want to permission as granularly as possible so the chain separation is actually a benefit!
0 reply
0 recast
0 reaction
Khỉ Út Nè
@khiutmkf
Maybe all module on all chain - what's da perfect move?
0 reply
0 recast
0 reaction
