A place for developers to talk about building on Farcaster.

/dev

why aren't siwe and siwf ubiquitous in auth solutions? by now I would have expected at least siwe to be everywhere as a plug-and-play adapter/provider, but it can only be found in an old nextauth tutorial for a custom implementation

Official siwe docs haven't been updated but generally speaking it's there in most wallet connector style libs

Rainbowkit has it, privy has it, pretty sure dynamic does too

leaving aside cloud-hosted services like privy and dynamic, rainbowkit locks you into nextauth. connectkit might be more flexible, I'm not sure.

my question is: if I go to the docs of open source self-hosted solutions like [betterauth / openauth / nextauth] why do I see little to no mention—let alone plug-and-play adaptors—for siwe, when decentralized identity is one of ethereum's main value prop?

I'm a bit puzzled that it hasn't become more popular as well. I'm hopeful that Stripe rolls out SIWE with their Pay with Crypto flow and Link, but I think Passkeys have become more favored because of auto-enrollment. The SIWE message signature always feel a bit spooky too because most wallets don't have custom Sign-in handling