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
94 reactions
Colin Johnson 💭
@cojo.eth
Does this get us closer to being able to authenticate with Privy in mini-apps?
2 replies
0 recast
2 reactions
Samuel ツ
@samuellhuber.eth
you could already do that if privy implemented something like https://dtech.vision/farcaster/frames/authentication-from-frames-with-nextauth/
1 reply
0 recast
2 reactions
Samuel ツ
@samuellhuber.eth
or if you on the backend hand out auth/session tokens manually (unsure if privy supports that)
1 reply
0 recast
2 reactions
Colin Johnson 💭
@cojo.eth
It's all front end from my understanding - hoping Privy gets something implemented here 🤞
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
What is all frontend ?
1 reply
0 recast
1 reaction
Ben Adamsky 💭
@ba
To clarify - Privy's auth is frontend, but we need wallet signing which uses their isolated iframe security model. Keys are only accessible during authenticated signing operations, never directly. So while Farcaster Connect helps with auth, we still need Privy's secure environment for smart wallet operations
1 reply
0 recast
1 reaction
Samuel ツ
@samuellhuber.eth
so you could authenticate the user, then send off to the backend for smart wallet actions. Backend calls privy and handles the wallet actions? would that work
1 reply
0 recast
1 reaction
Ben Adamsky 💭
@ba
SIWF auth via a miniapp response could work server-side, but from my understanding generating/signing with smart wallets still requires Privy's secure client iframe Fwiw it would be great for SIWF to work this way, would be a 10x improvement on auth experience similar to what neynar middleware did to frames
1 reply
0 recast
2 reactions
