Use standard e tag for attestations

This commit is contained in:
Jon Staab 2025-02-07 16:00:24 -08:00
parent a7bfdb398f
commit e2d6b7d165

7
03.md
View File

@ -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", "<event-id>", "<relay-url>", "<author-pubkey>"],
["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.