Content
@
0 reply
0 recast
0 reaction
Stephan
@stephancill
today you have to create a new signer for each device that you use with opencast on, which isn't great ux. would like to experiment with ways to address this without exposing user accounts to the risk of plaintext keys being stored in a centralized db some initial ideas 1. populate the signer from a passkey somehow (i think largeBlob enables this?) 2. metamask snap for farcaster signers (would also enable you to sign into many apps with the same signer) lmk if you have thoughts on this :)
6 replies
5 recasts
30 reactions
dylan
@dylsteck.eth
I think passkey should enable this & the largeBlob part of the passkey is where the mnemonic could be stored
1 reply
0 recast
1 reaction
Stephan
@stephancill
Just thinking about signers for now since opencast doesn’t deal with custody wallets directly yet. Passkeys could be a great way to do that though, ty. I think warpcast puts the mnemonic in largeBlob right?
0 reply
0 recast
1 reaction
