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?

Data privacy on the web. Keeper of the fabric @privy.

Fmr Protocol Labs consensus work. Before that YC S14 🇫🇷🌐🍊

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

> 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?

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.