From d43a3e46915c05a077a4f34188869d9b2bad2db6 Mon Sep 17 00:00:00 2001 From: kieran Date: Mon, 15 Apr 2024 11:21:18 +0100 Subject: [PATCH] Add previous tag --- 01.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/01.md b/01.md index a91febc..a85cdd0 100644 --- a/01.md +++ b/01.md @@ -99,6 +99,8 @@ And also a convention for kind ranges that allow for easier experimentation and In case of replaceable events with the same timestamp, the event with the lowest id (first in lexical order) should be retained, and the other discarded. +When the `previous` tag exists on a replaceable event relays SHOULD use this id as the id of the version the client wishes to replace, if the id does not match the stored version, relays MUST reject the update. + When answering to `REQ` messages for replaceable events such as `{"kinds":[0],"authors":[]}`, even if the relay has more than one version stored, it SHOULD return just the latest one. These are just conventions and relay implementations may differ.