So I guess you considered #Frost if you have been thinking about this for a long time but you haven't mentioned it. Why? Key rotation on the nsec level will hardly be a thing unless there's some cryptographic breakthrough because it would centralize the protocol, see PLC in atprotocol and such. You basically must centralize key lineage tracking to a trusted party but that just doesn't go well in a distributed system. Frost shard-based signing UX can be very stable and fairly revocable, it's just not yet spread so much. Social rotation is the other way, it's been talked about many times. It is a viable alternative in a network like nostr, especially if communities get more popular. The reason why there's not too much anxiety over this is just the fact that there's not yet enough demand I think for nostr in general. We're building things out and if there's real pressure in the future from economically relevant users accruing, at some point it's gonna be figured out.

Replies (1)

I’m not talking about key rotation. When I say delegation I mean “signing to approve other keys” so that client keys are ephemeral and specific to the client. In other words, my Nostr key only posts a list of attestation that say “these 10 keys are all me” same as I log into websites and say “these sessions are all mine” using cookies and account credentials. I’m not saying that’s foolproof or not without trade offs. As I said, I’m happy to hear about alternatives and don’t know why you jumped to “why are you ignoring Frost” like I’m aware there is some perfect solution and pretending it doesn’t exist on purpose. Specifically regarding frost, I’ve only loosely investigated it and how it could work with this UX issue. I thought of it as a different purpose tool but I think Max mentioned the same thing to me at one point but I haven’t had the time to get deep into it
↑