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

justice

Browse Source
This commit is contained in:
Pablo Fernandez 2023-11-16 19:11:46 +00:00
parent 68b27f6574
commit b6a524db0e
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
41.md
View File

@ -1,6 +1,6 @@
# NIP-41
## Key migration
`draft` `optional` `author:pablof7z` `author:fiatjaf`
`draft` `optional` `author:pablof7z` `author:fiatjaf` `author:nvk`
This NIP introduces a simple, best-effort, not guaranteed, way in which a user can notify their followers that they have migrated to a new public key in case the current one is compromised.
@ -87,4 +87,4 @@ Clients should keep track of when a `kind:1777` event should take into effect, c
Additionally, clients SHOULD broadcast the `kind:1777` events to the relays it normally writes to. This is to prevent an attacker from creating a short-lived NIP-65 relay list where only a subset of users will see an evil `kind:1777` event but not widespread enough for the real owner to notice it.
### Future Work
Key migration can be done in multiple ways. This is an initial implementation that can work. This mechanism should be extended with other, alternative mechanisms, that can leverage different flows/tradeoffs (e.g. social recovery).
Key migration can be done in multiple ways. This is an initial implementation that can work. This mechanism should be extended with other, alternative mechanisms, that can leverage different flows/tradeoffs (e.g. social recovery).