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

iirc there may be some answers to those questions in this video

this is great contains a lot of answers to my questions

for further reading
https://chainagnostic.org/CAIPs/caip-275
https://ethereum-magicians.org/t/erc-7555-single-sign-on-for-account-discovery/16536
https://eip.tools/eip/7715
https://erc7579.com/
https://ethereum-magicians.org/t/erc-7811-wallet-asset-discovery/21639

@payflow pay @stephancill 1 usdc for a useful answer

iirc there may be some answers to those questions in this video https://www.youtube.com/watch?v=FBB5YWMQ56s&t=335s

Wallet clients will likely limit you to one or a few battle-tested implementations. The risk is way too high for them if they give the user flexibility

abstractooor @rhinestone • prev oxford and exited web2 founder

so ERC-7579 aims to solve these problems by 1) having a function to discover account types and 2) standardising the core calldata (eg execution calldata) - its pretty widely adopted by biconomy, zerodev, trust wallet, thirdweb, safe support and more coming

Sure, what's the comment? Let me know and I'll try my best to reply. Have a great day!