Content pfp
Content
@
0 reply
20 recasts
20 reactions

Varun Srinivasan pfp
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
324 reactions

Corbin Page pfp
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

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
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.
3 replies
2 recasts
9 reactions

Stephan pfp
Stephan
@stephancill
Passkey wallet on keys.farcaster.xyz during onboarding the user enrols a passkey and the onboarding app enrols an EOA owner that it can use to do stuff in the background without constantly prompting the user for sigs (ideally with limited permissions via session keys) This way once the user is onboarded, apps can permissionlessly integrate passkey based sign in with farcaster and signer requests without needing the user to have warpcast installed Smart wallets and apps can make use of all the ERC4337 stuff like paymasters and bundlers. Could even be built in a way that allows apps to provide these as inputs Have built a prototype of this onboarding flow, needs some more polish before releasing
1 reply
1 recast
12 reactions

Martin  pfp
Martin
@koeppelmann.eth
EOAs are a dead end. Smart contract accounts are the solution (Safe). A ton of stuff is already working amazing (e.g. passkey as a owner, gas abstractions, gradual rights management). A few things are getting to maturity now around crosschain and recovery. The only larger so far still unsolved problem for SC is privacy - but even there is progress.
0 reply
0 recast
4 reactions

Kieran Daniels 🎩 pfp
Kieran Daniels 🎩
@kdaniels.eth
The ideal way to do this would be to generate a multisig for each new user as their account, warp has 1 signer, user has 2. But this is prob a bottom up rebuild and you’d need to do it all on base for gas costs.
0 reply
0 recast
2 reactions

Kieran Daniels 🎩 pfp
Kieran Daniels 🎩
@kdaniels.eth
Have you looked into apps that Encrypt the seed phrase into a hash and then store the hash on the users Secure Enclave? We built an iOS investment app that is similar to Farcaster in a lot of ways (not social whatsoever) and this was the only way we figured out 1. If users loses phone how to gain access 2. Switching between apps
3 replies
0 recast
2 reactions

Patricio Worthalter pfp
Patricio Worthalter
@worthalter
Another real problem of the current model is the trust assumptions around Sign In With Farcaster. In POAP we wanted to leverage SIWF but the way it’s designed makes it not be a fit for applications they require credibly robust authentication.
1 reply
0 recast
1 reaction

Erik pfp
Erik
@eriks
would love to see warpcast and base work together to embed a wallet here that has fiat onramping capability
0 reply
0 recast
0 reaction

wijuwiju.eth pfp
wijuwiju.eth
@wijuwiju.eth
Why do you think wallet UX is an existential problem for Farcaster?
0 reply
0 recast
0 reaction

Sinaver pfp
Sinaver
@sinaver.eth
1/2 I am wondering if you guys want to solve all 3 problems in one solution! Problem (1) will definitely require spinning off a smart contract (wallet) with limited signers authorisation for: - generating root level signers - generating cast level signers - accessing DC identity key and pre-keys (once it's decentralised) - spending keys if used for problems (2) and (3) (2) The problem is not only onboarding new users to a different wallet or fund it, the problem people have already funds in their wallets which they want to spend from, and existing infra very unlikely will use any embedded farcaster native smart wallet, unless it's based on an existing smart wallet infra! E.g. degen / moxie/ zora / hypersub are all bound to existing wallets to claim tokens which you want to spend.
1 reply
0 recast
3 reactions

Kurt pfp
Kurt
@kurtlarsen.eth
Hey Varun, We've done a lot of thinking about this at @rhinestone and it's formed the basis for a lot of the open source work we've done with Safe, zkSync, Biconomy, ZeroDev, OKX, and a number of others. The standard is called ERC-7579. This is a minimal standard for modular smart accounts. Modules are self-contained smart contracts that extend the functionality of a Smart Account. This will allow you to continue to support existing features (passkeys, gas abstraction, secure recovery mechanisms etc) but also provide new tools for the problems you raise. 1. If a user wants to change apps they can import the account and enable a new signer dedicated to that app or enable a session key to give the app scoped access. 2. No direct solution, but scoped executor modules and session keys can make this secure, whilst still open and programmable for applications. 3. Any developer can build a module, which under the right permissioning framework, can allow apps/users to extend the functionality of their account
0 reply
1 recast
1 reaction

jj πŸ›Ÿ pfp
jj πŸ›Ÿ
@jj
Why not just generate the wallet during sign up, back up to iCloud (but make it async/background) for now and only when they want to do off-ramp connect to Coinbase and do seed phrase (that’s the only time they care about doing the tedious task of managing seed phrases)
0 reply
0 recast
2 reactions

depatchedmode pfp
depatchedmode
@depatchedmode
I intend to turn my attention back to this problem set soon with the /secure-design group β€” which I've left on hiatus. Thx for the tight summary of your pov. I suspect interoperable delegation patterns like the sort @danfinlay and co are chasing lay at the heart of a better UX. To achieve a safe and secure version of this portability of authority, we really need to unfuck the authorization experience though. Bit of technical yack shaving still needed to get to the foothills of that problem.
1 reply
0 recast
4 reactions

WebOfTrust pfp
WebOfTrust
@weboftrust
for 1, what about cloud sync ? changing app - returning user - provide email - restore. Not ideal but better than copying the seed manually
0 reply
0 recast
0 reaction

Kyle McCollom pfp
Kyle McCollom
@kyle
I want: 1. To stay in Warpcast and complete transactions. 2. To use a global address that is not Warpcast-specific. I want to use this address in other apps too, I don't want yet another balance on a new address, and I want my friends to be able to follow what I do onchain. Building a good wallet is massively complex, and not something I feel like is going to move the needle for the Farcaster network. You should make a bet on web wallets like CBSW - it's what the majority of users will be using in ~2 years (other exchanges and wallets are launching equivalents soon). The experience is SO MUCH BETTER. No jumping between apps. No app download. No QR codes. No extensions. The experience is QC'd below. Signing screen can disappear with session keys. https://warpcast.com/jessepollak/0x2092e6a7
2 replies
0 recast
3 reactions

Icetoad 🎩 πŸ• 🎢 🐈 πŸ’š pfp
Icetoad 🎩 πŸ• 🎢 🐈 πŸ’š
@icetoad.eth
I guess account abstraction won't help when that comes into play with the next hard fork?
0 reply
0 recast
0 reaction

agusti 🐘 pfp
agusti 🐘
@bleu.eth
I always thought warpcast as a mobile wallet would make sense. All dapps are becoming wallets all wallets are becoming dapp browsers
0 reply
1 recast
0 reaction

WAGMI πŸŽ©πŸ˜‡ pfp
WAGMI πŸŽ©πŸ˜‡
@wagmi1337.eth
Just make add a non-custodial wallet to the Warpcast. it is not perfect, it is not safe, but it is the problem of a higher abstraction level => an operating systems level. So any solution on the app/protocol level won't be perfect. someday OS will have seed phrases vaults built-in and the problem will be gone, but for now it is the most easy go-to-solution. I mean a lot of viral crypto-apps were built this way (stepn, bonkbot, etc.) btw, will @kiosk ship a farcaster client with built-in wallet any time soon?
0 reply
0 recast
0 reaction

Adebisi Vince  pfp
Adebisi Vince
@adebisivince
Well don't know if it has been thought of, is this not where account abstraction comes in since no seed phrase is generated before you have an account
0 reply
0 recast
0 reaction