diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-02-13 08:47:23 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-02-13 08:47:23 -0300 |
| commit | b4493aa56abdea4b05780651e7af06ea13bbfafa (patch) | |
| tree | 1317e55dac8d3353cf1a5cba0947c826890953bf /33.md | |
| parent | a85067ec68f73ad72780dd2fba445bcaa1f5cba3 (diff) | |
rename coordinates: nitem->naddr, "i"->"a"
Diffstat (limited to '33.md')
| -rw-r--r-- | 33.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -38,11 +38,11 @@ Normally (as per NIP-01, NIP-12) the `"p"` tag is used for referencing public ke | |||
| 38 | equivalents for event tags (i.e. an `nprofile` is generally translated into a tag | 38 | equivalents 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 | ||
| 41 | To support linking to parameterized replaceable events, the `nitem` code is introduced on | 41 | To support linking to parameterized replaceable events, the `naddr` code is introduced on |
| 42 | NIP-19. It includes the public key of the event author and the `d` tag (and relays) such that | 42 | NIP-19. It includes the public key of the event author and the `d` tag (and relays) such that |
| 43 | the referenced combination of public key and `d` tag can be found. | 43 | the referenced combination of public key and `d` tag can be found. |
| 44 | 44 | ||
| 45 | The equivalent in `tags` to the `nitem` code is the tag `"i"`, comprised of `["i", "<kind>:<pubkey>:<d-identifier>", "<relay url>"]`. | 45 | The equivalent in `tags` to the `naddr` code is the tag `"a"`, comprised of `["a", "<kind>:<pubkey>:<d-identifier>", "<relay url>"]`. |
| 46 | 46 | ||
| 47 | Client Behavior | 47 | Client Behavior |
| 48 | --------------- | 48 | --------------- |