mleku on Nostr: to do key rotation (and for that matter, name resolution services) on nostr, you need ...

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 trust attestations (this is a non-token based distributed system architecture), they store and broadcast their events to be stored on relays and they use relays to rendezvous with peers instead of dealing with the network ingress difficulty caused by NAT routers.

this is the proposal that i've drafted for this, it uses a web of trust based design for relays to decide whether they will accept a registration or transfer of a name title to a new npub:

Free Internet Name Daemon (FIND): https://github.com/mleku/next.orly.dev/blob/main/docs/names.md