Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
jacopo.eth
@jacopo.eth
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
1 reply
1 recast
6 reactions
Haardik
@haardikkk
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
1 reply
0 recast
3 reactions
jacopo.eth
@jacopo.eth
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?
1 reply
0 recast
0 reaction
Daniel Sinclair
@danielsinclair
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
1 reply
0 recast
2 reactions
Daniel Sinclair
@danielsinclair
RainbowKit does support other auth frameworks beyond NextAuth btw! We adopted an adapter pattern to be a bit more flexible; the iron-session example uses this. It is still a bit challenging for devs to use, so I understand why Privy and Dynamic built around a centralized verifier. https://github.com/rainbow-me/rainbowkit/tree/main/examples/with-next-siwe-iron-session https://www.rainbowkit.com/docs/custom-authentication
2 replies
0 recast
2 reactions
Daniel Sinclair
@danielsinclair
Open to ideas if you think we can simplify this in any way! Most dApps that use this relied on wallet interactions, so we designed it for that use cases with Connect Wallet -> SIWE -> transaction signatures, but there is probably an opportunity for a drop-in SIWE-only flow as well for web2 auth flows.
1 reply
0 recast
2 reactions
jacopo.eth
@jacopo.eth
not directly related, but I still wish for a one-click connect & sign flow. it would significantly improve ux in many dapps like slice
1 reply
0 recast
2 reactions
Haardik
@haardikkk
That's mostly a wallet spec problem. I think @pedrouid.eth and walletconnect are cooking on that front
1 reply
0 recast
2 reactions
