From e2d6b7d16591b0af027e9d5765d6bf83d4a2c1c1 Mon Sep 17 00:00:00 2001 From: Jon Staab Date: Fri, 7 Feb 2025 16:00:24 -0800 Subject: [PATCH] Use standard e tag for attestations --- 03.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/03.md b/03.md index cf21c3ec..5e6f9118 100644 --- a/03.md +++ b/03.md @@ -44,7 +44,7 @@ timestamp validated at block [810391] Users MAY verify when they first saw an event by publishing a `kind:4341` event. -- One or more `stamp` tags MUST be included indicating event ids and timestamps. Event addresses MUST NOT be used. +- One or more `e` tags MUST be included indicating event ids and timestamps. Event addresses MUST NOT be used. - One or more `k` tags SHOULD be included indicating the kind(s) of the event(s) being referred to. - The `content` field MAY provide any human-readable explanation of the event. @@ -52,9 +52,10 @@ Users MAY verify when they first saw an event by publishing a `kind:4341` event. { "kind": 4341, "content": "I vaguely remember hearing about this note last year", + "created_at": 1738617405, "tags": [ ["alt", "A timestamp attestation event"], - ["stamp", "e71c6ea722987debdb60f81f9ea4f604b5ac0664120dd64fb9d23abc4ec7c323", 1738617405], + ["e", "", "", ""], ["k", "10002"] ] } @@ -62,4 +63,4 @@ Users MAY verify when they first saw an event by publishing a `kind:4341` event. Note that user-provided attestations provide a weaker guarantee than OTS proofs. Depending on the importance of the verification, multiple users with a good reputation should be consulted in order to determine a reasonable result. -Relays MAY also provide these attestations by generating and signing them on the fly using the pubkey listed in the relay's [NIP 11](./11.md) document. +Relays MAY also provide these attestations by generating and signing them on the fly using the `self` pubkey listed in the relay's [NIP 11](./11.md) document.