Thanks, I think including the signature will be a crucial im...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

fa9f48533dee8d2e259de890b6c68b01f59b2b3d841549b53eaa4967dcd6624e

nevent

nevent1qqs0486g2v77arfwykw73y9kc69sravm9v7cg92fk5l25jt8mntxynsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcmvj5fz

Kind-1 (TextNote)

2026-03-22T12:48:45Z

↳ 回复 事件不存在

e7088651b6f1d3fb6a63b69f8aa1e26e03f13f5f428e969cc60bb64a48491ee3...

Thanks, I think including the signature will be a crucial improvement to NIP-3.

FYI, for the example 31045 event that I pasted below, here's the string that was hashed for timestamping:

{"ID":"dbe68638908a66bb601f681b5a92a41d9fd9683fb97330a1f6e7f8fe687b4277","sig":"88a9c8fa5dd283ecbd279b4fa685e52538a56023e5b156888101e3bc110df10f10e18cc50929dc26c4357b8e1508eebc0690da6159bf29882f1233e2821efd2f"}

And here is the hash that was timestamped:

17c8b1d66c0d8d28b5c774036968804cb146d45785370a94cd43360f0ae0d169

You can verify this using the OTS proof in the content field of the event. If you're interested, I'm happy to send a quick script that produces this string and the hash from a given event_id and sig pair.

In my above list of tags that I recommend be included, I had forgotten to mention one: I think an s-tag for the signature of the target event should be included as well. This is necessary to be able to verify the "internal consistency" of the OTS event without needing to fetch the target event. The 31045 sample event I sent you includes this tag.

A few further thoughts on including p-tag, c-tag, s-tag, b-tag, t-tag : While working on Inkan I was frequently running into situations where I needed timestamp information quickly without fetching the target event and without doing a verification against Bitcoin. I realized that, in some circumstances, you can make limited trust assumptions regarding OTS events that are signed by trusted keys. Often you will trust the signer of the target event already to some extent, and if the OTS event is signed by the same signer, you can tentatively trust the content of the OTS event to a certain extent. For that reason, reading info like bitcoin block and bitcoin timestamp directly from tags in the OTS event can be quite helpful in practice in certain situations. And if there are any doubts as to the correctness of that information, you can always audit it against Bitcoin.

原始 JSON

{
  "kind": 1,
  "id": "fa9f48533dee8d2e259de890b6c68b01f59b2b3d841549b53eaa4967dcd6624e",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1774183725,
  "tags": [
    [
      "e",
      "e5b7ec9a5854b69c6d59ceea0c423d0f44d0996dcccd00764c174d8aa9e0162b",
      "wss://nos.lol/",
      "root",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "e",
      "e7088651b6f1d3fb6a63b69f8aa1e26e03f13f5f428e969cc60bb64a48491ee3",
      "wss://nos.lol/",
      "reply",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "p",
      "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451"
    ],
    [
      "p",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ]
  ],
  "content": "Thanks, I think including the signature will be a crucial improvement to NIP-3.\n\nFYI, for the example 31045 event that I pasted below, here's the string that was hashed for timestamping:\n\n{\"ID\":\"dbe68638908a66bb601f681b5a92a41d9fd9683fb97330a1f6e7f8fe687b4277\",\"sig\":\"88a9c8fa5dd283ecbd279b4fa685e52538a56023e5b156888101e3bc110df10f10e18cc50929dc26c4357b8e1508eebc0690da6159bf29882f1233e2821efd2f\"}\n\nAnd here is the hash that was timestamped:\n\n17c8b1d66c0d8d28b5c774036968804cb146d45785370a94cd43360f0ae0d169\n\nYou can verify this using the OTS proof in the content field of the event. If you're interested, I'm happy to send a quick script that produces this string and the hash from a given event_id and sig pair.\n\nIn my above list of tags that I recommend be included, I had forgotten to mention one: I think an s-tag for the signature of the target event should be included as well. This is necessary to be able to verify the \"internal consistency\" of the OTS event without needing to fetch the target event. The 31045 sample event I sent you includes this tag.\n\nA few further thoughts on including p-tag, c-tag, s-tag, b-tag, t-tag : While working on Inkan I was frequently running into situations where I needed timestamp information quickly without fetching the target event and without doing a verification against Bitcoin. I realized that, in some circumstances, you can make limited trust assumptions regarding OTS events that are signed by trusted keys. Often you will trust the signer of the target event already to some extent, and if the OTS event is signed by the same signer, you can tentatively trust the content of the OTS event to a certain extent. For that reason, reading info like bitcoin block and bitcoin timestamp directly from tags in the OTS event can be quite helpful in practice in certain situations. And if there are any doubts as to the correctness of that information, you can always audit it against Bitcoin.",
  "sig": "8ea17b26a1f0663f0a04bfd803626897243b82fd85d382499f198de03c304c6326d39882dea939bc640fc1613ac5cb4219313fe39734bfa8f3a0e3b72ecc30cc"
}