nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

feat: Adding field.

Browse Source
This commit is contained in:
jimbojw 2024-04-01 07:34:43 -04:00
parent 715e4a044d
commit fb883dba19
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
11.md
View File

@ -49,6 +49,18 @@ An alternative contact may be listed under the `contact` field as well, with the
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.
In addition, over time some `NIP`s are combined into other `NIP`s. For example, `NIP-01` now contains the features which were previously described separately by `NIP`s `12`, `16`, `20`, `22`, and `33`.
To clarify which versions of which `NIP`s a relay implements, the response MAY list a `supported_nips_at` field. If present, it MUST contain a unix timestamp in seconds as defined in [NIP-01](01.md). Changes to NIPs in the [nostr-protocol/nips](https://github.com/nostr-protocol/nips) repository after this time may not be supported.
```json
{
...
"supported_nips": [1, 11, 20],
"supported_nips_at": 1690848000,
}
```
### Software
The relay server implementation MAY be provided in the `software` attribute. If present, this MUST be a URL to the project's homepage.