Content
@
0 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
One advantage of SIWF over SIWE is that you don’t need to have 3+ different buttons / flows corresponding to different wallet providers Just scan a QR code, and you're authenticated I hope that as SIWF extends to other clients, the simplicity of having a single interface is maintained
5 replies
3 recasts
26 reactions
Samuel
@samuellhuber.eth
Yep authkit and the relay etc could all be run by other clients though currently to do it they need to provide a signature from the custody address which is why no one outside Warpcast bothers right now (no other client has enough active users where they control the custody address or the custody address isn’t Warpcast )
1 reply
0 recast
1 reaction
androidsixteen
@androidsixteen.eth
This will change over time though, but yeah the consolidation around one wallet app has been good for UX (and dev x)
1 reply
0 recast
1 reaction
Samuel
@samuellhuber.eth
It will yes, but by then it will still be the same QR (hopefully) and the deeplink will just open in the app the user has (please)
1 reply
0 recast
1 reaction
androidsixteen
@androidsixteen.eth
Wouldn’t this require an allowlist? How does the deeplink know which clients on the user’s device can be used for sign in?
1 reply
0 recast
0 reaction
Samuel
@samuellhuber.eth
The app registers for it. (Mobile) https://docs.mendix.com/howto8/mobile/native-deep-link/
1 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
No, I mean -- say I have 3 clients installed on my phone. How do you decide which one gets priority? Or are we expecting the app developer integrating SIWF to be aware of different clients and make that decision for the user?
1 reply
0 recast
0 reaction
Samuel
@samuellhuber.eth
Oh that’s different, would have to look into these cases
1 reply
0 recast
0 reaction
