Content
@
https://warpcast.com/~/channel/opencast
0 reply
0 recast
0 reaction
Stephan
@stephancill
cross platform login with a single signer and no backend has been achieved internally via largeblob (proof of cross-platform in reply)
7 replies
4 recasts
35 reactions
christopher
@christopher
are you using the sponsored/unsponsored signer flow from Warpcast to generate the key pair? cc @erica we will add this in to the auth flow
2 replies
0 recast
0 reaction
Stephan
@stephancill
I implemented wallet and warpcast signer flows. Wouldn’t copy and paste my implementations though lol
0 reply
0 recast
0 reaction
Stephan
@stephancill
Basically. Key generation happens locally, and then it sends the pubkey around for sigs Currently it’s just a button in a menu somewhere after you sign in. Will add to the create signer flow, but warning that support for largeBlob is kinda dodgy if you don’t use a password manager so it’s not fullproof Here’s the passkey business logic (can do with some refactoring and cleaning up still) https://github.com/stephancill/opencast/blob/main/src/lib/passkeys.ts Also just a heads up, passkeys don’t like non-https environments so I ended up using ngrok to test And another heads up, safari requires all passkey calls to be initiated by a user event so I ended up requiring the user to create the passkey and save the signer to largeBlob separately (https://github.com/stephancill/opencast/blob/main/src/components/modal/save-passkey-modal.tsx) there’s probs a better way Trigger warning: lots of spaghetti code in this repo lol
0 reply
0 recast
0 reaction
