finalize some NIPs we will not going to change anymore.

author: fiatjaf <fiatjaf@gmail.com> 2022-11-22 08:59:10 -0300
committer: fiatjaf <fiatjaf@gmail.com> 2022-11-22 14:52:34 -0300
commit: 743e43a8d4bf4a37022e3b6551524b12e7cc54a0 (patch)
tree: e0b3544e5d2dd07271059bb4d166c569cb89e425
parent: 631e9760bfa6ab44804a8ca28ca913dfacdbb5cc (diff)
5 files changed, 5 insertions, 5 deletions
diff --git a/02.md b/02.md
index 7309dd5..624d33f 100644
--- a/02.md
+++ b/02.md
@@ -4,7 +4,7 @@ NIP-02
 Contact List and Petnames
 -------------------------
-`draft` `optional` `author:fiatjaf` `author:arcbtc`
+`final` `optional` `author:fiatjaf` `author:arcbtc`
 A special event with kind `3`, meaning "contact list" is defined as having a list of `p` tags, one for each of the followed/known profiles one is following.
diff --git a/04.md b/04.md
index 801dd53..723bd70 100644
--- a/04.md
+++ b/04.md
@@ -4,7 +4,7 @@ NIP-04
 Encrypted Direct Message
 ------------------------
-`draft` `optional` `author:arcbtc`
+`final` `optional` `author:arcbtc`
 A special event with kind `4`, meaning "encrypted direct message". It is supposed to have the following attributes:
diff --git a/05.md b/05.md
index 1741aae..8aaa4d7 100644
--- a/05.md
+++ b/05.md
@@ -4,7 +4,7 @@ NIP-05
 Mapping Nostr keys to DNS-based internet identifiers
 ----------------------------------------------------
-`draft` `optional` `author:fiatjaf`
+`final` `optional` `author:fiatjaf`
 On events of type `0` (`set_metadata`) one can specify the key `"nip05"` with an [internet identifier](https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1) (an email-like address) as the value. Although there is a link to a very liberal "internet identifier" specification above, NIP-05 assumes the `<local-part>` part will be restricted to the characters `a-z0-9-_.`, case insensitive.
diff --git a/08.md b/08.md
index 99100c9..5dbb695 100644
--- a/08.md
+++ b/08.md
@@ -4,7 +4,7 @@ NIP-08
 Handling Mentions
 -----------------
-`draft` `optional` `author:fiatjaf` `author:scsibug`
+`final` `optional` `author:fiatjaf` `author:scsibug`
 This document standardizes the treatment given by clients of inline mentions of other events and pubkeys inside the content of `text_note`s.
diff --git a/15.md b/15.md
index 2a1c039..081a97d 100644
--- a/15.md
+++ b/15.md
@@ -4,7 +4,7 @@ NIP-15
 End of Stored Events Notice
 ---------------------------
-`draft` `optional` `author:Semisol`
+`final` `optional` `author:Semisol`
 Relays may support notifying clients when all stored events have been sent.
author	fiatjaf <fiatjaf@gmail.com>	2022-11-22 08:59:10 -0300
committer	fiatjaf <fiatjaf@gmail.com>	2022-11-22 14:52:34 -0300
commit	743e43a8d4bf4a37022e3b6551524b12e7cc54a0 (patch)
tree	e0b3544e5d2dd07271059bb4d166c569cb89e425
parent	631e9760bfa6ab44804a8ca28ca913dfacdbb5cc (diff)

diff --git a/02.md b/02.md index 7309dd5..624d33f 100644 --- a/02.md +++ b/02.md
@@ -4,7 +4,7 @@ NIP-02
4	Contact List and Petnames	4	Contact List and Petnames
5	-------------------------	5	-------------------------
6		6
7	`draft` `optional` `author:fiatjaf` `author:arcbtc`	7	`final` `optional` `author:fiatjaf` `author:arcbtc`
8		8
9	A special event with kind `3`, meaning "contact list" is defined as having a list of `p` tags, one for each of the followed/known profiles one is following.	9	A special event with kind `3`, meaning "contact list" is defined as having a list of `p` tags, one for each of the followed/known profiles one is following.
10		10


diff --git a/04.md b/04.md index 801dd53..723bd70 100644 --- a/04.md +++ b/04.md
@@ -4,7 +4,7 @@ NIP-04
4	Encrypted Direct Message	4	Encrypted Direct Message
5	------------------------	5	------------------------
6		6
7	`draft` `optional` `author:arcbtc`	7	`final` `optional` `author:arcbtc`
8		8
9	A special event with kind `4`, meaning "encrypted direct message". It is supposed to have the following attributes:	9	A special event with kind `4`, meaning "encrypted direct message". It is supposed to have the following attributes:
10		10


diff --git a/05.md b/05.md index 1741aae..8aaa4d7 100644 --- a/05.md +++ b/05.md
@@ -4,7 +4,7 @@ NIP-05
4	Mapping Nostr keys to DNS-based internet identifiers	4	Mapping Nostr keys to DNS-based internet identifiers
5	----------------------------------------------------	5	----------------------------------------------------
6		6
7	`draft` `optional` `author:fiatjaf`	7	`final` `optional` `author:fiatjaf`
8		8
9	On events of type `0` (`set_metadata`) one can specify the key `"nip05"` with an [internet identifier](https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1) (an email-like address) as the value. Although there is a link to a very liberal "internet identifier" specification above, NIP-05 assumes the `<local-part>` part will be restricted to the characters `a-z0-9-_.`, case insensitive.	9	On events of type `0` (`set_metadata`) one can specify the key `"nip05"` with an [internet identifier](https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1) (an email-like address) as the value. Although there is a link to a very liberal "internet identifier" specification above, NIP-05 assumes the `<local-part>` part will be restricted to the characters `a-z0-9-_.`, case insensitive.
10		10


diff --git a/08.md b/08.md index 99100c9..5dbb695 100644 --- a/08.md +++ b/08.md
@@ -4,7 +4,7 @@ NIP-08
4	Handling Mentions	4	Handling Mentions
5	-----------------	5	-----------------
6		6
7	`draft` `optional` `author:fiatjaf` `author:scsibug`	7	`final` `optional` `author:fiatjaf` `author:scsibug`
8		8
9	This document standardizes the treatment given by clients of inline mentions of other events and pubkeys inside the content of `text_note`s.	9	This document standardizes the treatment given by clients of inline mentions of other events and pubkeys inside the content of `text_note`s.
10		10


diff --git a/15.md b/15.md index 2a1c039..081a97d 100644 --- a/15.md +++ b/15.md
@@ -4,7 +4,7 @@ NIP-15
4	End of Stored Events Notice	4	End of Stored Events Notice
5	---------------------------	5	---------------------------
6		6
7	`draft` `optional` `author:Semisol`	7	`final` `optional` `author:Semisol`
8		8
9	Relays may support notifying clients when all stored events have been sent.	9	Relays may support notifying clients when all stored events have been sent.
10		10