mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-01-18 12:11:33 +00:00
add supported nips extended.
This commit is contained in:
parent
b809772bc3
commit
74c0189695
7
11.md
7
11.md
@ -19,6 +19,7 @@ When a relay receives an HTTP(s) request with an `Accept` header of `application
|
||||
"pubkey": <administrative contact pubkey>,
|
||||
"contact": <administrative alternate contact>,
|
||||
"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>,
|
||||
"version": <string version identifier>
|
||||
}
|
||||
@ -64,7 +65,11 @@ An alternative contact may be listed under the `contact` field as well, with the
|
||||
|
||||
### 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
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user