Yeah, I agree. That’s why my last attempt at key rotation wasn’t about key rotation at all, but about identity continuation. And I think not everyone, but some people might use it, specially entities or "high value" accounts. As I see it they would work more like a kind of change.org campaign. "Hey, this is my new key, there you have some proofs (wot voting, secret revelation, any other proof) that this is me and not an impersonator"

I just want to point out again that we have a fully functioning key revocation and replacement system in Nostr. I've been using it every day for months now. You can literally just head over to

Inkan

Inkan web client

and create an identity that can delegate signing authority to delegatee keys and revoke it when these keys are compromised. This enables cold storage identities for Nostr. If you want to see one of these identities in action, here is an example:

Inkan

Inkan web client

And here is the draft NIP that goes along with the reference implementation: View article →