Skip to content

Commit

Permalink
Merge pull request #20 from jiftechnify/nip-03
Browse files Browse the repository at this point in the history
NIP-03の翻訳
  • Loading branch information
jiftechnify authored Nov 12, 2023
2 parents a1baa9c + 9135bef commit 9d8e8e1
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions 03.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
NIP-03
======

OpenTimestamps Attestations for Events
イベントに対するOpenTimestamps認証
--------------------------------------

`draft` `optional` `author:fiatjaf` `author:constant`

This NIP defines an event with `kind:1040` that can contain an [OpenTimestamps](https://opentimestamps.org/) proof for any other event:
このNIPは`kind:1040`のイベントを定義します。これは他のイベントに対する[OpenTimestamps](https://opentimestamps.org/)証明を含むことができます。

```json
{
Expand All @@ -19,12 +19,12 @@ 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 `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.
- OpenTimestamps証明は、`e`タグで参照されているイベントを、そのIDをダイジェストとして証明しなければなりません(MUST)。
- `content`は、少なくとも1つのビットコイン認証を含む`.ots`ファイルの全内容でなければなりません(MUST)。このファイルは**単一の**ビットコイン認証のみを含み、かつ「未解決」の認証に対する参照を持たないべきです(SHOULD)。なぜなら、それらはこの状況では役に立たないからです。

### Example OpenTimestamps proof verification flow
### OpenTimestamps証明の検証フローの例

Using [`nak`](https://github.com/fiatjaf/nak), [`jq`](https://jqlang.github.io/jq/) and [`ots`](https://github.com/fiatjaf/ots):
[`nak`](https://github.com/fiatjaf/nak)[`jq`](https://jqlang.github.io/jq/)、そして[`ots`](https://github.com/fiatjaf/ots)コマンドを用います。

```bash
~> nak req -i e71c6ea722987debdb60f81f9ea4f604b5ac0664120dd64fb9d23abc4ec7c323 wss://nostr-pub.wellorder.net | jq -r .content | ots verify
Expand Down

0 comments on commit 9d8e8e1

Please sign in to comment.