finalize some NIPs we will not going to change anymore.

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.
 

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:
 

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.
 

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.
 

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.