laantungir
/
nips
mirror of https://github.com/nostr-protocol/nips.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add note about use of nip 89 handlers for dvm listings

This commit is contained in:
Jon Staab 2025-06-23 08:53:10 -07:00
parent 01d65d5f31
commit 82eeff3994
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
90.md
View File

@ -1,19 +1,19 @@
NIP-90
======
Service Providers
-----------------
Data Vending Machines
---------------------
`draft` `optional`
This NIP defines listings for service providers.
This NIP defines listings for service providers, AKA "Data Vending Machines".
## Flows
A flow is an independently-defined specification for how users ineract with a given service. The flow may be identified using any one of the following:
- A `NSP-XX` number, referring to a specification contained in this document, e.g. `["n", "NSP-01"]`.
- A url pointing to a web page containing a flow specification, e.g. `["n", "https://example.com/my-nsp"]`.
- A `DVM-XX` number, referring to a specification contained in this document, e.g. `["n", "DVM-01"]`.
- A url pointing to a web page containing a flow specification, e.g. `["n", "https://example.com/my-dvm"]`.
- A nostr event address pointing to any event which contains a flow specification, e.g. `["n", "<kind>:<pubkey>:<d>"]`.
Flow specifications MAY describe ANY flow, but SHOULD use nostr events as the primary means of communication between parties. Nostr events SHOULD specify the address of the `kind 31999` service announcement event when relevant, rather than the serivce provider's pubkey. Events SHOULD be posted to the recipient's inbox relays unless specified otherwise.
@ -46,6 +46,8 @@ Service Providers MAY use a `kind 31999` service announcement event to advertise
Flows MAY define additional tags that should be included on service announcement events.
Note that in the past DVMs were announced using kind `31990` application handler events, as defined in [NIP-89](./89.md). Publishing and consuming these events for DVMs is not recommended, but MAY be supported for backwards compatibility.
## Heartbeat Events
Service providers MAY publish kind `1999` heartbeat events to indicate service availability. Heartbeat events MUST include an `expiration` tag. The event's `content` MAY include human-readable information about the service's current status.
@ -65,7 +67,7 @@ Service providers MAY publish kind `1999` heartbeat events to indicate service a
## Flow Specifications
### NSP-01 - Content Discovery
### DVM-01 - Content Discovery
User publishes a `kind 5300` request for recommended content, including the following tags: