From 9bbf50551e175e2babfded27a8a811d05b4bdddd Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Wed, 3 Jan 2024 14:50:25 -0500 Subject: [PATCH] Adds description about the replaceable format. --- 01.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/01.md b/01.md index 309263b..b45887e 100644 --- a/01.md +++ b/01.md @@ -79,7 +79,7 @@ Specific ranges define storage behaviors: | Ephemeral | `20000 <= kind < 30000` | Nothing | | Parameterized | `30000 <= kind < 40000` | The newest event for each `pubkey`, `kind` and `d`-tag | -Parameterized Repleaceable events MUST include a `d`-tag with an identifier value to be used as reference. +Parameterized Repleaceable events MUST include a `d`-tag with an identifier value to be used as reference. Tag values want to reference the newest repleceable MUST use this format: `:<32-byte lowercase hex of a pubkey>:`. In case of replaceable events with the same timestamp, the event with the lowest `.id` (first in lexical order) SHOULD be retained. Older versions MAY be kept but SHOULD not be returned on queries. @@ -93,7 +93,7 @@ The first element of the tag array is referred to as the tag _name_ and the seco All single-letter (only English alphabet letters: a-z, A-Z) key tags are indexed by relays for faster queries. -This NIP defines the format of 3 standard tags: `e`, `p`, and `a`. `e`, `p` can be used to reference events and pubkeys, and `a` references the latest version of a replaceable event, parameterized or not. +This NIP defines the format of 3 standard tags: `e`, `p`, and `a`. `e`, `p` can be used to reference events and pubkeys respectivelly, and `a` references the latest version of a replaceable event, parameterized or not. Clients MAY `a`- and `e`-tag parameterized replaceables simultaneously. | Name | Value | Other Params | | ---- | ---------------------------------------------------------- | ------------------------ |