I don't have any power to change the protocol, all I can do is create a new protocol with different rules and I don't think that would help anyone.

Also dynamic keys introduce too many complications that ultimately make Nostr suck.

There are solutions to make our single keys safer. The main solution is called the bunker. And there are solutions to make it so that losing your main key isn't as bad as it may be currently. These solutions do not require creating a new protocol.

Also any scheme that involves key rotation or whatever still requires the concept of a "master" key. And that key has to be kept secure anyway, so you're really not solving anything.

Reply to this note

Please Login to reply.

Discussion

The solution should involve revoking the compromised key and linking it to the new one. Clients would then display notes from the old key up to the revocation point, and from the new key thereafter. If your key is compromised, revoke it and establish a link to the new one. Clients could follow the new key automatically or manually—it doesn't matter.

In this scenario who runs the key registries and how do you trust registry A vs B?

Why use registries? Just broadcast a revocation event to as many relays as possible. Key revoked.

If I steal your key and revoke it what happens then?

you saved me time by doing what i needed to do.

I control the key too and just tell everyone to follow my new account. You do the same. How is this resolved?

The same way as people identified you in the first place. Someone that knows IRL you can confirm your identity, or use nip05 to verify, or another social media, telegram, email, phone, whatever.