Merge 3338ae0eee8719e69e71805357b3fa4901841154 into 0619f370bca3485bb9c5870bc2defa03c7c3d10e

This commit is contained in:
dbth 2025-03-22 14:46:07 +09:00 committed by GitHub
commit 77fa8e642a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

5
90.md
View File

@ -18,6 +18,7 @@ This NIP reserves the range `5000-7000` for data vending machine use.
| 5000-5999 | Job request kinds |
| 6000-6999 | Job result |
| 7000 | Job feedback |
| 7007 | Ping |
Job results always use a kind number that is `1000` higher than the job request kind. (e.g. request: `kind:5001` gets a result: `kind:6001`).
@ -176,9 +177,13 @@ Service providers can give feedback about a job back to the customer.
| `error` | Service Provider was unable to process the job. |
| `success` | Service Provider successfully processed the job. |
| `partial` | Service Provider partially processed the job. The `.content` might include a sample of the partial results. |
| `pong` | Service Provider signals it's alive in response to a Kind 7007 Ping Request |
Any job feedback event MIGHT include results in the `.content` field, as described in the [Job Result](#job-result-kind6000-6999) section. This is useful for service providers to provide a sample of the results that have been processed so far.
### DVM Ping request
DVMs should implement a listener for Kind 7007, which is defined as a Ping command. The DVM should reply to a ping command with a Kind 7000 feedback event with status "pong" and optional more details about the DVM in the content field. This allows clients to check if a DVM is currently running, without sending an actual job request to the DVM (triggering a job, requesting an invoice etc).
# Protocol Flow