to do key rotation (and for that matter, name resolution services) on nostr, you need a consensus protocol. the actual consensus would be an independent server that does the chatter sharing the relays...
@mleku is a smart cookie, and has a nice proposal. But (like Rustr’s proposal also) this problem is not going to be solved by only ONE technique for key management / rotation / expiration / ect … there will be many. There MUST be many.
Nostr’s existential challenge is NOT to find consensus around single NIP for any one problem … but to allow for dynamism (having a variety of techniques in use simultaneously) WITHOUT overly burdening users or developers in the process.
This is where WoT comes in. Most solutions (for any problem) will lean on WoT (in some manner) as a proxy for truth. Without assuming any one WoT technique will be “the WoT NIP”, ANY WoT should be able to “truthfully” demonstrate that “this is indeed Alice’s new npub”.
Nostr’s existential challenge is NOT to find consensus around single NIP for any one problem … but to allow for dynamism (having a variety of techniques in use simultaneously) WITHOUT overly burdening users or developers in the process.
This is where WoT comes in. Most solutions (for any problem) will lean on WoT (in some manner) as a proxy for truth. Without assuming any one WoT technique will be “the WoT NIP”, ANY WoT should be able to “truthfully” demonstrate that “this is indeed Alice’s new npub”.
1
