Keys are a huge problem.
One solution is a NIP for designating a backup NPUB, as soon as you create your original one. This designation must be immutable.
Then, if NPUB 1 is breached, user presses the big red button to engage NPUB2. Forming the equivalent of a 301 redirect on Nostr.
Since the NPUB 2 designation was made before the hijack, it doesn't matter if a hijacker has access to NPUB 1. The original user can still press big red button, migrating to NPUB 2 which hijacker can't control.
Login to reply
Replies (2)
Interesting idea. So you get a second chance if you lose your private key.
How do you know what happened before what?
The timestamp in Nostr events is not certified by default. It's only signed as part of the event, you can post from the past and from the future if you want.
Would that require certifying timestamps, thus adding more complexity? Consider this is aimed at the dumbest users, the most likely to paste their nsec where they shouldn't.