0 reply
20 recasts
20 reactions
25 replies
66 recasts
324 reactions
5 replies
2 recasts
13 reactions
3 replies
2 recasts
9 reactions
1 reply
1 recast
12 reactions
0 reply
0 recast
4 reactions
0 reply
0 recast
2 reactions
3 replies
0 recast
2 reactions
1 reply
0 recast
1 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
1 reply
0 recast
3 reactions
Hey Varun,
We've done a lot of thinking about this at @rhinestone and it's formed the basis for a lot of the open source work we've done with Safe, zkSync, Biconomy, ZeroDev, OKX, and a number of others.
The standard is called ERC-7579. This is a minimal standard for modular smart accounts. Modules are self-contained smart contracts that extend the functionality of a Smart Account. This will allow you to continue to support existing features (passkeys, gas abstraction, secure recovery mechanisms etc) but also provide new tools for the problems you raise.
1. If a user wants to change apps they can import the account and enable a new signer dedicated to that app or enable a session key to give the app scoped access.
2. No direct solution, but scoped executor modules and session keys can make this secure, whilst still open and programmable for applications.
3. Any developer can build a module, which under the right permissioning framework, can allow apps/users to extend the functionality of their account 0 reply
1 recast
1 reaction
0 reply
0 recast
2 reactions
1 reply
0 recast
4 reactions
0 reply
0 recast
0 reaction
2 replies
0 recast
3 reactions
0 reply
0 recast
0 reaction
0 reply
1 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction