mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-09-20 06:45:49 -04:00
Add claim
tag to AUTH
This commit is contained in:
parent
f3a2356484
commit
cbcb49fdcf
12
42.md
12
42.md
|
@ -36,7 +36,17 @@ And, when sent by clients, the following form:
|
||||||
|
|
||||||
### Canonical authentication event
|
### Canonical authentication event
|
||||||
|
|
||||||
The signed event is an ephemeral event not meant to be published or queried, it must be of `kind: 22242` and it should have at least two tags, one for the relay URL and one for the challenge string as received from the relay. Relays MUST exclude `kind: 22242` events from being broadcasted to any client. `created_at` should be the current time. Example:
|
The signed event is an ephemeral event of `kind: 22242` and it should have at least two tags, one for the relay URL,
|
||||||
|
and one containing evidence of access. This may be one of:
|
||||||
|
|
||||||
|
- `challenge` - the challenge string recieved from the relay.
|
||||||
|
- `claim` - an arbitrary token exchanged out-of-band. Relays SHOULD store this authorization so that the `challenge`
|
||||||
|
method can be used in the future.
|
||||||
|
|
||||||
|
Clients MUST NOT publish these events. Relays MUST exclude `kind: 22242` events from being broadcasted to any client.
|
||||||
|
Relays MUST validate that `created_at` is the current time, adjusting for clock skew.
|
||||||
|
|
||||||
|
Example:
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
|
|
Loading…
Reference in New Issue
Block a user