Farcaster Devs

Something that concerns me about the fc signer architecture is how it increases the attack surface area for your account the more apps you allow to sign on your behalf

This limits the propensity for users to try new apps especially if they have a large audience

Solutions: portable signers? Permissions? Sessions?

best farcaster developers build on neynar.com | /neynar

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

I think @neynar is close to releasing something similar to scoped keys for their signer flow.

Another option that’s immediately available but not pretty is custody keys where you control a pair and use them in different apps, like an API key. Was planning on making a front end for this repo so people can do that

Full Stack Dev | Head of Developer Relations at /pinata | Technical Writer | Tinkering with everything | stevedylan.dev/links

Another option that’s immediately available but not pretty is custody keys where you control a pair and use them in different apps, like an API key. Was planning on making a front end for this repo so people can do that

https://github.com/stevedylandev/farcaster-keys-server

🪐 Building @neynar, join us in /neynar

Everyday regular normal guy | 👨‍💻 @neynar ...

Yes we’ll have keys scoped to more granular permissions cc @manan @shreyas-chorge

this is good for users but it’s bad that it needs to happen at this part of the stack. Creates pretty large centralization / platform / lock-in risk