nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 16:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

mute mute

Browse Source
This commit is contained in:
Pablo Fernandez 2023-10-19 16:44:42 +03:00
parent d6074050e6
commit b86ad6f627
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
41.md
View File

@ -51,8 +51,7 @@ When the user needs to change keys they sign an event `kind:1777` with the new k
[ "e", "<kind:1776-event-id>" ], [ "e", "<kind:1776-event-id>" ],
[ "proof", "<kind:1040-event-id>" ], [ "proof", "<kind:1040-event-id>" ],
[ "alt", "pubkey migration event" ], [ "alt", "pubkey migration event" ],
[ "relays", "relay1", "relay2" ], [ "relays", "relay1", "relay2" ]
[ "mute" ]
] ]
} }
``` ```
@ -61,7 +60,6 @@ When the user needs to change keys they sign an event `kind:1777` with the new k
* `e` tag MUST list the `kind:1776` event that whitelisted the new pubkey. * `e` tag MUST list the `kind:1776` event that whitelisted the new pubkey.
* `proof` tag MUST list the `kind:1040` event that provides the Opentimestamp data of the `kind:1776` event. * `proof` tag MUST list the `kind:1040` event that provides the Opentimestamp data of the `kind:1776` event.
* `relays` tag SHOULD list relays where both `kind:1776` and `kind:1040` events can be found. * `relays` tag SHOULD list relays where both `kind:1776` and `kind:1040` events can be found.
* `mute` is optional If it's present, clients SHOULD mute the old pubkey. Users who are migrating because of a compromised key can use this to protect their followers.
* `.content` SHOULD be ignored; users can optionally write a message explaining the migration. * `.content` SHOULD be ignored; users can optionally write a message explaining the migration.
## Following the new pubkey ## Following the new pubkey