NIP-03
======
OpenTimestamps Attestations for Events
--------------------------------------
`draft` `optional` `author:fiatjaf`
When there is an OTS available it MAY be included in the existing event body under the `ots` key:
```
{
"id": ...,
"kind": ...,
...,
...,
"ots": <base64-encoded OTS file data>
}
```
The _event id_ MUST be used as the raw hash to be included in the OpenTimestamps merkle tree.
The attestation can be either provided by relays automatically (and the OTS binary contents just appended to the events it receives) or by clients themselves when they first upload the event to relays — and used by clients to show that an event is really "at least as old as [OTS date]".
loverx
npub1q8…2j54x
2023-03-26 12:41:00
Author Public Key
npub1q84yw2skdp4jmearzldkpwjv6ry0efdsm8q84zhu4xt4s2dmxfzq62j54xPublished at
2023-03-26 12:41:00Event JSON
{
"id": "e7bccdb51e98b50195c70724dc47cb8cee7ef815bc38b71a6e8dd5c7855e4e91",
"pubkey": "01ea472a16686b2de7a317db60ba4cd0c8fca5b0d9c07a8afca9975829bb3244",
"created_at": 1679834460,
"kind": 1,
"tags": [],
"content": "NIP-03\n======\n\nOpenTimestamps Attestations for Events\n--------------------------------------\n\n`draft` `optional` `author:fiatjaf`\n\nWhen there is an OTS available it MAY be included in the existing event body under the `ots` key:\n\n```\n{\n \"id\": ...,\n \"kind\": ...,\n ...,\n ...,\n \"ots\": \u003cbase64-encoded OTS file data\u003e\n}\n```\n\nThe _event id_ MUST be used as the raw hash to be included in the OpenTimestamps merkle tree.\n\nThe attestation can be either provided by relays automatically (and the OTS binary contents just appended to the events it receives) or by clients themselves when they first upload the event to relays — and used by clients to show that an event is really \"at least as old as [OTS date]\".",
"sig": "cfbc6421f6ea5cd8bc01e1d1b0532a8f7e8409f967a25adc498a20a47322082c2a1b93c0cd7d83a75f01e88c9e35f28572a38d88879f149b304472bc21e5bfbf"
}