Mirror/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-01-18 20:21:35 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

add supported nips extended.

Browse Source
This commit is contained in:
Kay 2025-01-03 13:27:35 +00:00
parent b809772bc3
commit 74c0189695
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
11.md
View File

@ -19,6 +19,7 @@ When a relay receives an HTTP(s) request with an `Accept` header of `application
"pubkey": <administrative contact pubkey>, "pubkey": <administrative contact pubkey>,
"contact": <administrative alternate contact>, "contact": <administrative alternate contact>,
"supported_nips": <a list of NIP numbers supported by the relay>, "supported_nips": <a list of NIP numbers supported by the relay>,
"supported_nips_extended": <a list of NIP numbers supported by the relay in string format to support nips with hex numbers>,
"software": <string identifying relay software URL>, "software": <string identifying relay software URL>,
"version": <string version identifier> "version": <string version identifier>
} }
@ -64,7 +65,11 @@ An alternative contact may be listed under the `contact` field as well, with the
### Supported NIPs ### Supported NIPs
As the Nostr protocol evolves, some functionality may only be available by relays that implement a specific `NIP`. This field is an array of the integer identifiers of `NIP`s that are implemented in the relay. Examples would include `1`, for `"NIP-01"` and `9`, for `"NIP-09"`. Client-side `NIPs` SHOULD NOT be advertised, and can be ignored by clients. For NIPs with a hexadecimal number, relays MUST consider using the decimal representation of the same number. As the Nostr protocol evolves, some functionality may only be available by relays that implement a specific `NIP`. This field is an array of the integer identifiers of `NIP`s that are implemented in the relay. Examples would include `1`, for `"NIP-01"` and `9`, for `"NIP-09"`. Client-side `NIPs` SHOULD NOT be advertised, and can be ignored by clients.
#### Supported NIPs Extended
There are some NIPs with a hexadecimal number which can't fit into `supported_nips`, the `supported_nips_extended` fields contains strings instead of numbers and it can include NIPs with hexadecimal number.
### Software ### Software