From c2ae0c416b78260c5d94bf17250c0fb525d73633 Mon Sep 17 00:00:00 2001 From: Dustin Dannenhauer Date: Thu, 11 Jan 2024 21:01:45 +0000 Subject: [PATCH] Update 90.md protocol flow --- 90.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/90.md b/90.md index b48a36bb..9ce9cb3f 100644 --- a/90.md +++ b/90.md @@ -208,7 +208,7 @@ Customers can give feedback about a job result back to the service provider via * Service Providers MAY submit `kind:7000` job-feedback events (e.g. `payment-required`, `processing`, `error`, etc.). * Upon completion, the service provider publishes the result of the job with a `kind:6000` job-result event. * At any point, if there is an `amount` pending to be paid as instructed by the service provider, the user can pay the included `bolt11` or zap the job result event the service provider has sent to the user -* (optional) Customer publishes a customer feedback `kind:8000` event +* (optional) Customer publishes a customer feedback `kind:7` event Job feedback (`kind:7000`) and Job Results (`kind:6000-6999`) events MAY include an `amount` tag, this can be interpreted as a suggestion to pay. Service Providers MUST use the `payment-required` feedback event to signal that a payment is required and no further actions will be performed until the payment is sent.