upleb.uk

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

summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorfiatjaf <fiatjaf@gmail.com>2023-01-16 08:28:02 -0300
committerGitHub <noreply@github.com>2023-01-16 08:28:02 -0300
commitbe0a426745252eeb420a38e4896b28059b4f7fa5 (patch)
tree36e5991a370c60a0f0ccc1d52a7e0b11ffcdd735 /README.md
parente5ae318984bdc2f28932420be976183c9a0cd3ff (diff)
parent60741160535de8137fb7a74bd6561adef974b884 (diff)
Merge pull request #141 from nostr-protocol/auth
Diffstat (limited to 'README.md')
-rw-r--r--README.md14
1 files changed, 9 insertions, 5 deletions
diff --git a/README.md b/README.md
index 10bb5ef..5dec5f1 100644
--- a/README.md
+++ b/README.md
@@ -28,6 +28,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
28- [NIP-33: Parameterized Replaceable Events](33.md) 28- [NIP-33: Parameterized Replaceable Events](33.md)
29- [NIP-36: Sensitive Content](36.md) 29- [NIP-36: Sensitive Content](36.md)
30- [NIP-40: Expiration Timestamp](40.md) 30- [NIP-40: Expiration Timestamp](40.md)
31- [NIP-42: Authentication of clients to relays](42.md)
31 32
32## Event Kinds 33## Event Kinds
33 34
@@ -47,6 +48,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
47| 43 | Channel Hide Message | [28](28.md) | 48| 43 | Channel Hide Message | [28](28.md) |
48| 44 | Channel Mute User | [28](28.md) | 49| 44 | Channel Mute User | [28](28.md) |
49| 45-49 | Public Chat Reserved | [28](28.md) | 50| 45-49 | Public Chat Reserved | [28](28.md) |
51| 22242 | Client Authentication | [42](42.md) |
50| 10000-19999 | Replaceable Events Reserved | [16](16.md) | 52| 10000-19999 | Replaceable Events Reserved | [16](16.md) |
51| 20000-29999 | Ephemeral Events Reserved | [16](16.md) | 53| 20000-29999 | Ephemeral Events Reserved | [16](16.md) |
52 54
@@ -54,11 +56,12 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
54## Message types 56## Message types
55 57
56### Client to Relay 58### Client to Relay
57| type | description | NIP | 59| type | description | NIP |
58|-------|-----------------------------------------------------|------------| 60|-------|-----------------------------------------------------|-------------|
59| EVENT | used to publish events | [1](01.md) | 61| EVENT | used to publish events | [1](01.md) |
60| REQ | used to request events and subscribe to new updates | [1](01.md) | 62| REQ | used to request events and subscribe to new updates | [1](01.md) |
61| CLOSE | used to stop previous subscriptions | [1](01.md) | 63| CLOSE | used to stop previous subscriptions | [1](01.md) |
64| AUTH | used to send authentication events | [42](42.md) |
62 65
63### Relay to Client 66### Relay to Client
64| type | description | NIP | 67| type | description | NIP |
@@ -67,6 +70,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
67| NOTICE | used to send human-readable messages to clients | [1](01.md) | 70| NOTICE | used to send human-readable messages to clients | [1](01.md) |
68| EOSE | used to notify clients all stored events have been sent | [15](15.md) | 71| EOSE | used to notify clients all stored events have been sent | [15](15.md) |
69| OK | used to notify clients if an EVENT was successuful | [20](20.md) | 72| OK | used to notify clients if an EVENT was successuful | [20](20.md) |
73| AUTH | used to send authentication challenges | [42](42.md) |
70 74
71Please update these lists when proposing NIPs introducing new event kinds. 75Please update these lists when proposing NIPs introducing new event kinds.
72 76