Tony D’Addeo
@deodad
smart wallet question I assume there will be a handful of popular implementations with a long tail of more experimental stuff. how much of a challenge will it be for a wallet client to support getting a signer to any one of the implementations and interacting with it? how would the wallet discover the implementation? inspecting onchain state or asking the user? what sorts of differences are there between contracts in terms of doing basic interactions?
6 replies
2 recasts
8 reactions
Tony D’Addeo
@deodad
cc @henri
1 reply
0 recast
0 reaction
Henri Stern Ꙫ
@henri
Yes! There will need to be new JSON-RPC interfaces for dapps to get information about smart wallets (like implementation and what it supports). wallet_getCapabilities is already one that exists today that can be used to determine if gas can be sponsored etc. for external smart wallets. From there, we're already seeing a handful of popular implementations & a long tail. Currently it's less "wallet discovering the implementation" (which is what 7555 helps with!) and more "this is the implementation I want/will be using" (and dApps/wallet providers track that to then offer the same one deterministically to the user). 4337 has defines the standard for basic interactions for which there's little delta for the end user.
1 reply
0 recast
2 reactions
Tony D’Addeo
@deodad
> Currently it's less "wallet discovering the implementation" (which is what 7555 helps with!) and more "this is the implementation I want/will be using" (and dApps/wallet providers track that to then offer the same one deterministically to the user). Would you elaborate on this?
1 reply
0 recast
0 reaction
Henri Stern Ꙫ
@henri
Today, the vast majority of smart wallets are embedded signers integrated by dapps themselves, so apps already know which smart account implementation, contracts, etc. that are being used under the hood (they chose to use that particular smart wallet implementation). At Privy, we're pushing on making smart wallets work better in a cross-app setting though (eg as part of our ecosystem SDKs) and as part of this, are pushing on JSON-RPC interfaces to make it possible for dapps to discover information about smart wallets they connect to, like the wallet_getCapabilities call, for instance enabling an ecosystem app to add alternate signers to the smart wallet etc. This is very much the tip of the spear today but evolving quickly. Also paging @gregthegreek.eth who has been thinking about this a fair bit :D
1 reply
0 recast
1 reaction
GregTheGreek
@gregthegreek.eth
highhhhly suggest you watch this 12 minute video. I think i did a great job at articulating the problems and the path forward https://www.youtube.com/watch?v=FBB5YWMQ56s
2 replies
0 recast
1 reaction
Henri Stern Ꙫ
@henri
On it! TY!!!
0 reply
0 recast
1 reaction
