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

Improves the wording

Browse Source
This commit is contained in:
Vitor Pamplona 2024-02-17 17:56:33 -05:00
parent 1e888d99cc
commit f91d82425b
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
22.md
View File

@ -6,7 +6,9 @@ Key Migration
`draft` `optional` `draft` `optional`
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. 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.
```js ```js
{ {
@ -19,9 +21,13 @@ Kind 18 informs the network that the owner of the pubkey is migrating to a new k
} }
``` ```
`Kind:18`s suggestion to move to a new key **alone** can't be trusted because the owner's keys might have leaked. It MUST be verified by Web of Trust. ## Confirmation Chains
Close acquaintances to the owner should verify the intention off nostr and signal their assessment of the owner's intentions by following the new key. Others can follow based on their individual trust on such those acquaintances. Since the owner's keys might have leaked, `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.
## Interpretation ## Interpretation
@ -29,7 +35,7 @@ The presence of one or more `kind:18`s, no matter who writes it, declares the ke
Users that have a `kind:18` published by their keys MUST migrate to a new key. 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 keys. Finding which event is the right one requires observing contact lists of trusted keys. 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