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 :)
5 replies
2 recasts
21 reactions
andrew
@boop
Blatant shill: Privy Farcaster signers are self custodial/only within the browser but recoverable on other devices. With our new cross-app release theoretically you can also share signers across apps, but that’s more of a stretch right now. I think storing in passkey large blob could be effective for personal use but due to platform inconsistency atm, won’t work well more generally (I’m pretty sure Warpcast also does not use them like this for same reason). Otherwise I think Metamask snap is interesting, although I’m always a little hesitant to add them and I’ve heard approval process isn’t straightforward rightfully due to the sensitivity
1 reply
0 recast
2 reactions
Stephan
@stephancill
Thanks for the feedback :) You guys are doing great work keeping farcaster users safe. Is the privy solution self hostable?
1 reply
0 recast
0 reaction
andrew
@boop
We aren't :( We do have examples of open source projects (ie dydx) that just put the app ID in the repo as a get started and our global rate limit is pretty lenient, and you can create different app clients with more or less restrictive rulesets
0 reply
0 recast
0 reaction
