Content
@
0 reply
20 recasts
20 reactions
Varun Srinivasan
@v
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!
25 replies
66 recasts
323 reactions
Corbin Page
@corbin.eth
I’ve thought about this a lot: All good UX crypto apps will have an embedded wallet. This is pretty clear now and will be best practice next cycle. You can roll your own (as you have) or use WaaS provider like @privy @web3auth etc. 1 - This is a feature for advanced users. Put it in Settings. Most users will just send all their assets to an external wallet anyway vs exporting the key. 2 - Chain abstraction solves this and you can still do in-app Apple payment for value+gas and it gets executed via a solver network. No need to have native tokens in EOA on all chains. 3 - Most users just want to do simple transactions. Keep it simple and let advanced users export seed. In my opinion, you can solve this whole problem with the Verified Addresses feature. Allow users to create WC embedded wallets there and set which one the app should prioritize for Frame/app actions. They can manage their current FC EOA and/or sign up for a Privy embedded wallet and set their preference.
5 replies
2 recasts
13 reactions
Corbin Page
@corbin.eth
You can offer a super simple UX for new / non crypto users and advanced users can still default to an external wallet. You can even have smart contract wallets there as an account type if you want to but keep it simple to start. Smart contract wallets still lack a lot of protocol support, are hard to manage across all chains, and require workarounds for non EVM chains. Embedded EOAs + chain abstraction services give you all the same benefits. The decision is whether to prioritize expanding your current embedded EOA functionality or going with WaaS like Privy. The benefit of using WaaS is that you don’t have to build ancillary features like recovery, permissions/session key stuff, etc and can focus on core value. You give up some control though.
0 reply
1 recast
4 reactions
