Farcaster

Wallet UX is an existential problem for Farcaster. 

If we don't make it easy for users to do things onchain and easy for developers to build farcaster apps, we can't scale the network. 

We're thinking about solutions right now, but want to share the problem statement the team is thinking about. Feedback welcome!

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Would it make sense to have a multisig with 1/n for every user? Then each app will have to use their EOA, but one of the other apps will have to add it to the multisg.

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

Do consumers care if a multisig is classified as a smart contract wallet or not? In this case, most of them will never even know. The question is if this setup could work, or if it breaks other flows.

I think world is moving from multisigs to smart contract wallets for consumer use cases?

Supercast: "Do you want to allow Supercast to manage your multisig? Yes/No"
Warpcast: "Supercast has requested access to your multisig. Approve/Deny"

This is actually a really clever idea 

Have a top-level address that's a pointer at all the app-specific addresses