While I'm at it – another proof that nostr devs aren't serious about adoption is still the lack of key rotation.
I get it. It's a big task and can't be solved by any individual client, it needs t...
Well, I did it some time ago. Nobody cared, just as with the others.
I’m not claiming this is the right way, but after studying Nostr for a while, I concluded that key rotation cannot be handled automatically or authoritatively in a decentralized system. Contact list migration and Web of Trust persistence introduce significant risks, and no universal authority can conclusively determine whether a new key belongs to the same identity after key loss or compromise.
My latest attempt was Checkpoints. The goal was to standardize a minimal, interoperable way to publish identity continuity claims and optional supporting evidence. Clients can then discover and users evaluate these claims using cryptographic and social corroboration.
Identity continuity in Nostr is ultimately observer-dependent, so Checkpoints standardize claims and evidence, not truth. The aim is to avoid ad hoc, application-specific approaches without defining an automatic or deterministic migration rule. The already classic kind 1 saying 'My new key is X' done right, or at least and attempt of it
https://github.com/nostr-protocol/nips/pull/2278
Announced it during #soveng 6, never released the app since nobody cared
I’m not claiming this is the right way, but after studying Nostr for a while, I concluded that key rotation cannot be handled automatically or authoritatively in a decentralized system. Contact list migration and Web of Trust persistence introduce significant risks, and no universal authority can conclusively determine whether a new key belongs to the same identity after key loss or compromise.
My latest attempt was Checkpoints. The goal was to standardize a minimal, interoperable way to publish identity continuity claims and optional supporting evidence. Clients can then discover and users evaluate these claims using cryptographic and social corroboration.
Identity continuity in Nostr is ultimately observer-dependent, so Checkpoints standardize claims and evidence, not truth. The aim is to avoid ad hoc, application-specific approaches without defining an automatic or deterministic migration rule. The already classic kind 1 saying 'My new key is X' done right, or at least and attempt of it
https://github.com/nostr-protocol/nips/pull/2278
Announced it during #soveng 6, never released the app since nobody cared
12❤️1🫂2👀1💜1
