Web3 newsletters & publishing.

We automatically summarize and cast about the best posts on Paragraph.

Live The Game. Real-time, immersive social markets for sports & live events. /bracket

Since FC hub data is public, what's the benefit of using SIWF over connecting with a wallet and associating a FC account (like @paragraph @bracketgame et al), and just pulling the social graph / content as needed?

Especially since connecting a wallet is more decentralized than doing OAuth facilitated by Warpcast?

it's one tap for siwf vs two with siwe, assuming all users have warpcast (which mine do, at least right now)

founder of eventcaster (@event / events.xyz), hosting /latenightcrew, member of 🍊 dao

For your use case, it makes more sense - you’re not targeting any audiences outside of Warpcast (at least initially)

What about for builders / apps targeting a broader crypto audience?

Or even if they are focused on Farcaster, the optionality seems useful since FC isn’t huge yet

yeah in that case, especially if you want to prompt txns, it makes sense to do siwe and just associate the fid. then you have the eoa connected to prompt txns.

if / when eventcaster adds non-fc signups, I'd probably offer both options.

best farcaster developers build on neynar.com | /neynar

for builders an interseting compromise is siwn (@neynar) so you can reuse previously authorized signers by 35k userbase neynar already has

this make it 1 step if they're already preauthed in any neynar signer based app