the TL;DR is:

* you publish a whitelisting event for your next npub, the event is timestamped (NIP-03)

* when your account is compromised you publish a migration event from your new key

whatever valid migration event points to the oldest (unforgeable due to timestamping) whitelisting event wins

Reply to this note

Please Login to reply.

Discussion

I like the sound of this.

What if the attacker publishes the migration event first?

you get a 60-day time window to publish a new migration event pointing to an older one

full spec: https://github.com/nostr-protocol/nips/pull/829

Thanks. I'll give it a read.

For the sake of being overly paranoid, the new key now holds a lot of power and must be tightly guarded and kept track of even though not in use, as it could at any time be used by anyone who has it to invalidate the old account. New fear unlocked 😅 But I like that it could at least be an option.

yeah, but being careful with that key would be so much easier because you are not using it actively so there's no reason to go crazy entering the nsec in a million places

True.