nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-13 23:39:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge branch 'key-rotation' of https://github.com/vitorpamplona/nips into key-rotation

Browse Source 
# Conflicts:
#	22.md
This commit is contained in:
Vitor Pamplona 2024-02-17 18:11:33 -05:00
commit c78e79e9cd
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
22.md
View File

@ -6,7 +6,7 @@ Key Migration
`draft` `optional`
Kind 18 informs the network that the owner of the pubkey is migrating to a new key.
`Kind:18` informs the network that the owner of the pubkey is migrating to a new key.
The event MUST contain a single `p` tag with the new pubkey owner will be using.
@ -23,21 +23,21 @@ The event MUST contain a single `p` tag with the new pubkey owner will be using.
## Confirmation Chains
Since the owner's keys might have leaked, `Kind:18`s **alone** can't be trusted.
Since the owner's keys might have leaked and this event might come from an attacker, `Kind:18`s **alone** can't be trusted.
Close acquaintances to the owner should verify the owner's intention off nostr and signal their conclusion by adding the new key to their contact lists.
Others can follow based on their individual trust on such those acquaintances.
Others may choose to follow suit based on their trust in such acquaintances.
## Interpretation
The presence of one or more `kind:18`s, no matter who writes it, declares the key to be out of use, unreliable, unsafe and potentially stolen: No event, past and future, from this key can be trusted anymore.
The presence of one or more `kind:18`s, no matter who writes it, declares the key to be out of use, unreliable, unsafe, and potentially stolen: No event, past and future, from this key can be trusted anymore.
Users that have a `kind:18` published by their keys MUST migrate to a new key.
There can be multiple `kind:18`s pointing to separate new keys. Finding which event is the right one requires observing contact lists of trusted keys.
## Information retention
## Information Retention
Clients SHOULD send `kind:18` to as many relays as possible, not only to the owner's relay list.