upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/47.md
diff options
context:
space:
mode:
authorYasuhiro Matsumoto <mattn.jp@gmail.com>2023-06-26 10:37:48 +0900
committerfiatjaf_ <fiatjaf@gmail.com>2023-06-26 14:55:24 -0300
commitfab6a21a779460f696f11169ddf343b437327592 (patch)
tree0336dac8335befc7d185a961d540c7dd9d004676 /47.md
parent852bd7f8723227edce9f64d8492c3afa000af97f (diff)
fixed typos
Diffstat (limited to '47.md')
-rw-r--r--47.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/47.md b/47.md
index c884b97..b6a4f2b 100644
--- a/47.md
+++ b/47.md
@@ -33,7 +33,7 @@ There are three event kinds:
33- `NIP-47 response`: 23195 33- `NIP-47 response`: 23195
34 34
35The info event should be a replaceable event that is published by the **wallet service** on the relay to indicate which commands it supports. The content should be 35The info event should be a replaceable event that is published by the **wallet service** on the relay to indicate which commands it supports. The content should be
36a plaintext string with the supported commands, space-seperated, eg. `pay_invoice get_balance`. Only the `pay_invoice` command is described in this NIP, but other commands might be defined in different NIPs. 36a plaintext string with the supported commands, space-separated, eg. `pay_invoice get_balance`. Only the `pay_invoice` command is described in this NIP, but other commands might be defined in different NIPs.
37 37
38Both the request and response events SHOULD contain one `p` tag, containing the public key of the **wallet service** if this is a request, and the public key of the **user** if this is a response. The response event SHOULD contain an `e` tag with the id of the request event it is responding to. 38Both the request and response events SHOULD contain one `p` tag, containing the public key of the **wallet service** if this is a request, and the public key of the **user** if this is a response. The response event SHOULD contain an `e` tag with the id of the request event it is responding to.
39 39
@@ -64,8 +64,8 @@ Response:
64``` 64```
65 65
66The `result_type` field MUST contain the name of the method that this event is responding to. 66The `result_type` field MUST contain the name of the method that this event is responding to.
67The `error` field MUST contain a `message` field with a human readable error message and a `code` field with the error code if the command was not succesful. 67The `error` field MUST contain a `message` field with a human readable error message and a `code` field with the error code if the command was not successful.
68If the command was succesful, the `error` field must be null. 68If the command was successful, the `error` field must be null.
69 69
70### Error codes 70### Error codes
71- `RATE_LIMITED`: The client is sending commands too fast. It should retry in a few seconds. 71- `RATE_LIMITED`: The client is sending commands too fast. It should retry in a few seconds.