diff options
Diffstat (limited to '42.md')
| -rw-r--r-- | 42.md | 6 |
1 files changed, 3 insertions, 3 deletions
| @@ -20,19 +20,19 @@ A relay may want to require clients to authenticate to access restricted resourc | |||
| 20 | 20 | ||
| 21 | ### New client-relay protocol messages | 21 | ### New client-relay protocol messages |
| 22 | 22 | ||
| 23 | This NIP defines a new message, `AUTH`, which relays can send when they support authentication and clients can send to relays when they want to authenticate. When sent by relays, the message is of the following form: | 23 | This NIP defines a new message, `AUTH`, which relays CAN send when they support authentication and clients can send to relays when they want to authenticate. When sent by relays the message has the following form: |
| 24 | 24 | ||
| 25 | ```json | 25 | ```json |
| 26 | ["AUTH", <challenge-string>] | 26 | ["AUTH", <challenge-string>] |
| 27 | ``` | 27 | ``` |
| 28 | 28 | ||
| 29 | And, when sent by clients, of the following form: | 29 | And, when sent by clients, the following form: |
| 30 | 30 | ||
| 31 | ```json | 31 | ```json |
| 32 | ["AUTH", <signed-event-json>] | 32 | ["AUTH", <signed-event-json>] |
| 33 | ``` | 33 | ``` |
| 34 | 34 | ||
| 35 | `AUTH` messages sent by clients should be answered with an `OK` message, like any `EVENT` message. | 35 | `AUTH` messages sent by clients MUST be answered with an `OK` message, like any `EVENT` message. |
| 36 | 36 | ||
| 37 | ### Canonical authentication event | 37 | ### Canonical authentication event |
| 38 | 38 | ||