Moves embeds outside the TLV

This commit is contained in:
Vitor Pamplona 2024-02-27 11:05:04 -05:00
parent 713bea60c2
commit d33727da81

3
19.md
View File

@ -19,6 +19,7 @@ These are the possible bech32 prefixes:
- `npub`: public keys - `npub`: public keys
- `nsec`: private keys - `nsec`: private keys
- `note`: note ids - `note`: note ids
- `nembed`: JSON-stringified, GZIP-compressed event
Example: the hex public key `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d` translates to `npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6`. Example: the hex public key `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d` translates to `npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6`.
@ -36,7 +37,6 @@ These are the possible bech32 prefixes with `TLV`:
- `nevent`: a nostr event id - `nevent`: a nostr event id
- `nrelay`: a nostr relay - `nrelay`: a nostr relay
- `naddr`: a nostr _replaceable event_ coordinate - `naddr`: a nostr _replaceable event_ coordinate
- `nembed`: a compressed nostr event
These possible standardized `TLV` types are indicated here: These possible standardized `TLV` types are indicated here:
@ -46,7 +46,6 @@ These possible standardized `TLV` types are indicated here:
- for `nevent` it will be the 32 bytes of the event id - 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 `naddr`, it is the identifier (the `"d"` tag) of the event being referenced. For non-parameterized replaceable events, use an empty string. - for `naddr`, it is the identifier (the `"d"` tag) of the event being referenced. For non-parameterized replaceable events, use an empty string.
- for `nembed`, it is a JSON-stringified, GZIP-compressed event
- `1`: `relay` - `1`: `relay`
- for `nprofile`, `nevent` and `naddr`, _optionally_, a relay in which the entity (profile or event) is more likely to be found, encoded as ascii - for `nprofile`, `nevent` and `naddr`, _optionally_, a relay in which the entity (profile or event) is more likely to be found, encoded as ascii
- this may be included multiple times - this may be included multiple times