remove useless "block" tag on OTS.

This commit is contained in:
fiatjaf 2023-10-17 07:38:53 -03:00
parent 202e18f2b2
commit cf672b764b
No known key found for this signature in database
GPG Key ID: BAD43C4BE5C1A3A1

2
03.md
View File

@ -13,7 +13,6 @@ This NIP defines an event with `kind:1040` that can contain an [OpenTimestamps](
"kind": 1040 "kind": 1040
"tags": [ "tags": [
["e", <event-id>, <relay-url>], ["e", <event-id>, <relay-url>],
["block", <block-height-as-string>, <block-hash>],
["alt", "opentimestamps attestation"] ["alt", "opentimestamps attestation"]
], ],
"content": <base64-encoded OTS file data> "content": <base64-encoded OTS file data>
@ -21,7 +20,6 @@ This NIP defines an event with `kind:1040` that can contain an [OpenTimestamps](
``` ```
- The OpenTimestamps proof MUST prove the referenced `e` event id as its digest. - The OpenTimestamps proof MUST prove the referenced `e` event id as its digest.
- The `block` tag is optional, it exists to establish a minimum date since which the given event has existed.
- The `content` MUST be the full content of an `.ots` file containing at least one Bitcoin attestation. This file SHOULD contain a **single** Bitcoin attestation and no reference to "pending" attestations since they are useless in this context. - The `content` MUST be the full content of an `.ots` file containing at least one Bitcoin attestation. This file SHOULD contain a **single** Bitcoin attestation and no reference to "pending" attestations since they are useless in this context.
### Example OpenTimestamps proof verification flow ### Example OpenTimestamps proof verification flow