From 8545dce4eca23c597f1fdb818eaf80614da27126 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Wed, 26 Nov 2025 15:32:58 -0500 Subject: [PATCH 1/2] Simper key migration --- A1.md | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 A1.md diff --git a/A1.md b/A1.md new file mode 100644 index 0000000000..fd9735d74b --- /dev/null +++ b/A1.md @@ -0,0 +1,36 @@ +NIP-A1 +====== + +Key Migration +------------- + +`draft` `optional` + +This NIP offers a simple mechanism to socially evaluate and authenticate a key migration. + +Users publish kind `39` events when migrating to a new key (`p` tag). + +```yaml +{ + "kind": 39, + "pubkey": "
", // The old/main public key + "tags": [ + ["p", ""] // The new public key + ], + content: "", + // Other fields +} +``` + +Kind `39` events are either a legitimate migration and should be accepted, or a phishing attempt +by an attacker, which should be rejected and the main key unfollowed. + +[NIP-22](22.md) comments SHOULD be used to debate if the event is legitimate. [NIP-56](56.md) reports +can be used to reveal malicious behavior. + +Clients SHOULD offer Web of Trust signals to help users make a decision. + +Clients SHOULD emphasize off-line verification procedures when a kind `39` is found. + +Clients MAY offer easy functions to switch the user's follow lists to the new public key and +revert the transaction if necessary. \ No newline at end of file From 61f9e75ed63f1fb1bf29cd8257d33f6938b38148 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Tue, 2 Dec 2025 13:30:01 -0500 Subject: [PATCH 2/2] Removing NIP-56 It's too complicated already --- A1.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/A1.md b/A1.md index fd9735d74b..4de707c32a 100644 --- a/A1.md +++ b/A1.md @@ -6,7 +6,7 @@ Key Migration `draft` `optional` -This NIP offers a simple mechanism to socially evaluate and authenticate a key migration. +This NIP offers a simple mechanism to evaluate and authenticate a key migration socially. Users publish kind `39` events when migrating to a new key (`p` tag). @@ -23,14 +23,13 @@ Users publish kind `39` events when migrating to a new key (`p` tag). ``` Kind `39` events are either a legitimate migration and should be accepted, or a phishing attempt -by an attacker, which should be rejected and the main key unfollowed. +by an attacker, which should be rejected, and the main key unfollowed. -[NIP-22](22.md) comments SHOULD be used to debate if the event is legitimate. [NIP-56](56.md) reports -can be used to reveal malicious behavior. +[NIP-22](22.md) comments SHOULD be used to debate if the event is legitimate. Clients SHOULD offer Web of Trust signals to help users make a decision. Clients SHOULD emphasize off-line verification procedures when a kind `39` is found. Clients MAY offer easy functions to switch the user's follow lists to the new public key and -revert the transaction if necessary. \ No newline at end of file +revert the transaction if necessary.