From b86ad6f627114961f4c676edafc8194a449fbdab Mon Sep 17 00:00:00 2001 From: Pablo Fernandez Date: Thu, 19 Oct 2023 16:44:42 +0300 Subject: [PATCH] mute `mute` --- 41.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/41.md b/41.md index ad50400f..2783903f 100644 --- a/41.md +++ b/41.md @@ -51,8 +51,7 @@ When the user needs to change keys they sign an event `kind:1777` with the new k [ "e", "" ], [ "proof", "" ], [ "alt", "pubkey migration event" ], - [ "relays", "relay1", "relay2" ], - [ "mute" ] + [ "relays", "relay1", "relay2" ] ] } ``` @@ -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. * `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. -* `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. ## Following the new pubkey