upleb.uk

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

summaryrefslogtreecommitdiff
path: root/33.md
diff options
context:
space:
mode:
Diffstat (limited to '33.md')
-rw-r--r--33.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/33.md b/33.md
index 5b8ad66..409ce4f 100644
--- a/33.md
+++ b/33.md
@@ -38,11 +38,11 @@ Normally (as per NIP-01, NIP-12) the `"p"` tag is used for referencing public ke
38equivalents for event tags (i.e. an `nprofile` is generally translated into a tag 38equivalents for event tags (i.e. an `nprofile` is generally translated into a tag
39`["p", "<event hex id>", "<relay url>"]`). 39`["p", "<event hex id>", "<relay url>"]`).
40 40
41To support linking to parameterized replaceable events, the `nitem` code is introduced on 41To support linking to parameterized replaceable events, the `naddr` code is introduced on
42NIP-19. It includes the public key of the event author and the `d` tag (and relays) such that 42NIP-19. It includes the public key of the event author and the `d` tag (and relays) such that
43the referenced combination of public key and `d` tag can be found. 43the referenced combination of public key and `d` tag can be found.
44 44
45The equivalent in `tags` to the `nitem` code is the tag `"i"`, comprised of `["i", "<kind>:<pubkey>:<d-identifier>", "<relay url>"]`. 45The equivalent in `tags` to the `naddr` code is the tag `"a"`, comprised of `["a", "<kind>:<pubkey>:<d-identifier>", "<relay url>"]`.
46 46
47Client Behavior 47Client Behavior
48--------------- 48---------------