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:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft (who else) had one that I’m not sure was ever merged but is in use. It involves creating an event defining a future key you might need to rotate to and then open timestamping that event to “notarize” the time.

I have some sort of odd mental block on remembering the number or the site on this one but I’m sure Pablo can fill in the blanks.

Reply to this note

Please Login to reply.

Discussion

This is the latest spin on that idea: https://github.com/nostr-protocol/nips/pull/1032

I need to keep working on it to make it simpler 🫡

Oh nice! Hadn’t seen this yet!