diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-11-18 08:22:42 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-11-18 08:22:42 -0300 |
| commit | 7aa751be46d515d7612998a4da88285cb0957cd3 (patch) | |
| tree | 80e10127de95552adcba69627f4504ddda6ca6e8 | |
| parent | b5b46b629fb1b4dae4780d8d165bddd68d4cda68 (diff) | |
NIP-03: explain why a single attestation is recommended.
| -rw-r--r-- | 03.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -20,7 +20,7 @@ This NIP defines an event with `kind:1040` that can contain an [OpenTimestamps]( | |||
| 20 | ``` | 20 | ``` |
| 21 | 21 | ||
| 22 | - The OpenTimestamps proof MUST prove the referenced `e` event id as its digest. | 22 | - The OpenTimestamps proof MUST prove the referenced `e` event id as its digest. |
| 23 | - 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. | 23 | - 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 (as not more than one valid attestation is necessary and less bytes is better than more) and no reference to "pending" attestations since they are useless in this context. |
| 24 | 24 | ||
| 25 | ### Example OpenTimestamps proof verification flow | 25 | ### Example OpenTimestamps proof verification flow |
| 26 | 26 | ||