nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

nip-42 phrasing.

Browse Source
This commit is contained in:
fiatjaf 2023-12-07 21:18:45 -03:00
parent 730324f487
commit ef106eccca
No known key found for this signature in database
GPG Key ID: BAD43C4BE5C1A3A1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
42.md
View File

@ -20,19 +20,19 @@ A relay may want to require clients to authenticate to access restricted resourc
### New client-relay protocol messages ### New client-relay protocol messages
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: 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:
```json ```json
["AUTH", <challenge-string>] ["AUTH", <challenge-string>]
``` ```
And, when sent by clients, of the following form: And, when sent by clients, the following form:
```json ```json
["AUTH", <signed-event-json>] ["AUTH", <signed-event-json>]
``` ```
`AUTH` messages sent by clients should be answered with an `OK` message, like any `EVENT` message. `AUTH` messages sent by clients MUST be answered with an `OK` message, like any `EVENT` message.
### Canonical authentication event ### Canonical authentication event