nostr/nips
0
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-09-01 05:50:47 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

NIP-23: long-form content.

Browse Source
This commit is contained in:
fiatjaf
2023-02-03 15:59:07 -03:00
parent 025beb332c
commit 7c444e3474
3 changed files with 84 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
19.md
View File

@@ -35,6 +35,7 @@ These are the possible bech32 prefixes with `TLV`:
- `nprofile`: a nostr profile
- `nevent`: a nostr event
- `nrelay`: a nostr relay
- `nref`: a nostr parameterized replaceable event coordinate (NIP-33)
These possible standardized `TLV` types are indicated here:
@@ -42,11 +43,15 @@ These possible standardized `TLV` types are indicated here:
- depends on the bech32 prefix:
- for `nprofile` it will be the 32 bytes of the profile public key
- for `nevent` it will be the 32 bytes of the event id
- for `nrelay`, this is the relay URL.
- for `nrelay`, this is the relay URL
- for `nref`, it is the identifier (the `"d"` tag) of the event being referenced
- for `nprofile`, `nevent` and `nrelay` this may be included only once.
- `1`: `relay`
- A relay in which the entity (profile or event) is more likely to be found, encoded as UTF-8. This may be included multiple times.
- not applicable to `nrelay`.
- for `nprofile`, `nevent` and `nref`, a relay in which the entity (profile or event) is more likely to be found, encoded as UTF-8. This may be included multiple times
- `2`: `author`
- for `nref`, the 32 bytes of the pubkey of the event
## Examples
- `npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6` should decode into the public key hex `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d` and vice-versa