Content
@
0 reply
0 recast
0 reaction
Varun Srinivasan
@v
FIP: Farcaster Connect An update to the Sign in with Farcaster (FIP-11) proposal to support request from wallets other than Warpcast. Feedback welcome! https://github.com/farcasterxyz/protocol/discussions/204
7 replies
26 recasts
158 reactions
Haole
@haole
👀👀 CC @patxol.eth @edisonchen
1 reply
0 recast
0 reaction
patxol 🔷 anser.social
@patxol.eth
That's cool for clients that embed wallets and great for client diversity. Not usable for @anser-social.eth but that's normal.
1 reply
0 recast
1 reaction
Haole
@haole
Hmm, I think we’ll have to rely on Neynar to implement that for now since we don’t control the user’s signer yet. I remember someone proposed a new design in Hub v2 to make app connections free. If that happens, I will control the signer directly in my app.
1 reply
0 recast
0 reaction
patxol 🔷 anser.social
@patxol.eth
With the proposed implementation, event Neynar cannot control it. Farcaster Connect like SIWF is a wallet action. If you do not have the private keys of the custody wallet, you can't do it. At least that's my understanding. Yopu would have to have wallet capabilities and the custody address to perform Farcaster Connect with Recaster.
1 reply
0 recast
0 reaction
rish
@rish
neynar doesn't have to "control" it, it just has to route to the app that is the custody wallet. it routes to Warpcast today and it can allow options to route to other things in the future Signers are always generated via custody wallets. SIWF assumed the only custody wallet is Warpcast and now it will be a broader set. SIWN will accept the signer generation from whichever app is the custody wallet
2 replies
0 recast
2 reactions
