#[2] #[3] fyi
Discussion
this is really cool, although I'm not sure how many people are going to setup a successor key and keep it safe before their secret key gets leaked
I like the idea of setting it up before hand as a solution to the hacker front-running the real users event though.
also it might not be necessary for relays to reject newer 101 events if clients dont look for the latest event. then again its possible the attacker could post a backdated event
Maybe key A and B can be derived from the same master key C which the user stores (so that B is like another derivation path?)
Maybe this could be handled by, the client and switching to B would just be pressing of an emergency button in the
settings
This is just me spitballing, but maybe its only necessary to have an event type that says "this key is compromised" then its up to the client/user to find the new pubkey through their social circle.
Then maybe there could be a new kind of event that would be published by anyone which would say "X's new key is Y". then the client could gather these events from your followers or random strangers? and show the user a few options (hopefully just one) for a new pubkey to follow. almost like a social voting system? idk