Replying to Avatar Guy Swann

There should be a key change NIP for Nostr.

Could be interesting too if you had it so that you had designated accounts to confirm a key change too. Like I would use my brother nostr:npub1ajv7m32k0cpgzha32qszsh304qusjvwwmavus0ttktzldms4xzusuftppj and maybe nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 or someone else I know really well in the space as “trusted verifiers.” Then if my key ever got stolen, even though both myself and the hacker could sign, I could make it so only I could transfer it to a new key by asking my verifiers to sign.

Maybe that’s too convoluted, but I feel like there should be a key cycling method regardless.

nostr:npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds is your guy: https://github.com/nostr-protocol/nips/pull/1032

Reply to this note

Please Login to reply.

Discussion

"Social proof(optional): the event contains a list of people that the master keypair attaches to the revocation certificate as `p` tags. These pubkeys are designated as trusted identities that can judge/signal if the new proposed identity is trustworthy or not"