air217 on Nostr: Hmm one way to do key rotation on Nostr could be to follow both the NIP-05 verified ...
Hmm one way to do key rotation on Nostr could be to follow both the NIP-05 verified domain + npub key
For example, if I follow Jack, instead of following only his npub, we follow his (npub, nip-05 domain).
Now let's say the key somehow gets compromised, but the NIP-05 domain that we subscribed to at the time of follow no longer is verifying the compromised npub, then we unfollow Jack.
And when I want to add Jack again, clients can promote Jack's new npub by crawling his domain (which we assume he will not lose control of).
I think breaking chain of trust when an identification anomaly is detected is great for trust. As long the actions made are transparent to the user
Published at
2023-07-25 02:34:38Event JSON
{
"id": "67f6c75a5d161840f4f91d7c3c58b8ff7b35d6ba2ef185dac56954244d4549e0",
"pubkey": "d3916f42beae421694ce03938c32f4f71f967b05068b01d713b461165bdd6446",
"created_at": 1690252478,
"kind": 1,
"tags": [
[
"client",
"coracle"
]
],
"content": "Hmm one way to do key rotation on Nostr could be to follow both the NIP-05 verified domain + npub key\n\nFor example, if I follow Jack, instead of following only his npub, we follow his (npub, nip-05 domain). \n\nNow let's say the key somehow gets compromised, but the NIP-05 domain that we subscribed to at the time of follow no longer is verifying the compromised npub, then we unfollow Jack. \n\nAnd when I want to add Jack again, clients can promote Jack's new npub by crawling his domain (which we assume he will not lose control of). \n\nI think breaking chain of trust when an identification anomaly is detected is great for trust. As long the actions made are transparent to the user",
"sig": "aba3c42ec946a3aa28cc16262f76a2c0adcedae6ab214822d33ce097843ed58955bd40f8a530bb6dff4ff5dd2032ce4670d290d3b5cf4f22bf5256821d57652d"
}