arbedout on Nostr: I think NIP-05 gets us most of the way there - rotate your keys associated with your ...
I think NIP-05 gets us most of the way there - rotate your keys associated with your NIP-05 identifier and other users will discover your new keys quickly enough - but how clients handle that is up to them. (been focused on running a relay, not sure if any clients have hashed out how to handle NIP-05 "collisions").
There's also NIP-26, which seems like overkill - with that you could e.g. have a master key that delegates signing to a key, and revokes delegation if the key is compromised.
Published at
2023-01-26 22:26:50Event JSON
{
"id": "cdce8910738dbfcc7a2f51257b1015e8ab3c657faa02d24bd691c2f364a3cdc0",
"pubkey": "a67e98faf32f2520ae574d84262534e7b94625ce0d4e14a50c97e362c06b770e",
"created_at": 1674772010,
"kind": 1,
"tags": [
[
"e",
"cdff98a10796c77e7ca37dc8a81de17f78938e45ba43bb26043311810f0dbcab",
"",
"root"
],
[
"e",
"619629f9381d9ed78267ce4e178801e97e568fb625de241c7047e0141556cd5e",
"",
"reply"
],
[
"p",
"c7eda660a6bc8270530e82b4a7712acdea2e31dc0a56f8dc955ac009efd97c86"
]
],
"content": "I think NIP-05 gets us most of the way there - rotate your keys associated with your NIP-05 identifier and other users will discover your new keys quickly enough - but how clients handle that is up to them. (been focused on running a relay, not sure if any clients have hashed out how to handle NIP-05 \"collisions\").\n\nThere's also NIP-26, which seems like overkill - with that you could e.g. have a master key that delegates signing to a key, and revokes delegation if the key is compromised.",
"sig": "db5d53ec1215d766bc1d9acef1f3332587886402e20721394caa6ce9e6cee5de1b3085e764978f4246a326295ba2849246fd99a950cc7c9ea245f35fb2ff4aaa"
}
