1 files changed, 2 insertions, 2 deletions
diff --git a/41.md b/41.md
index 1642590..9260e97 100644
--- a/41.md
+++ b/41.md
@@ -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).
-\ No newline at end of file
+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).

diff --git a/41.md b/41.md index 1642590..9260e97 100644 --- a/41.md +++ b/41.md
@@ -1,6 +1,6 @@
1	# NIP-41	1	# NIP-41
2	## Key migration	2	## Key migration
3	`draft` `optional` `author:pablof7z` `author:fiatjaf`	3	`draft` `optional` `author:pablof7z` `author:fiatjaf` `author:nvk`
4		4
5	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.	5	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.
6		6
@@ -87,4 +87,4 @@ Clients should keep track of when a `kind:1777` event should take into effect, c
87	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.	87	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.
88		88
89	### Future Work	89	### Future Work
90	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). \ No newline at end of file	90	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).