If NIP-3 is going to change, the most important thing to inc...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

ec35aee7b9a3ef7f4d98a2a0910288c79d8d6a54e13bdf41a71ed2a83c41111f

nevent

nevent1qqswcddwu7u68mmlfkv29gy3q2yv08vddf2wzw7lgxn3a54g83q3z8cprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gc4zcrpy

Kind-1 (TextNote)

2026-03-21T23:44:18Z

↳ 回复 事件不存在

e5b7ec9a5854b69c6d59ceea0c423d0f44d0996dcccd00764c174d8aa9e0162b...

If NIP-3 is going to change, the most important thing to incorporate into the updated specification is that the item that gets timestamped must include both the event_id and the signature of the target event. I think including the signature is quite crucial. See below for discussion with nostr:npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds about this issue.

The ideal shape for an OTS event should also include something like a p-tag for the pubkey of the target event, a c-tag for the created_at time of the target event, a b-tag for the bitcoin block that anchors the timestamp, and a t-tag for the time of that bitcoin block.

I'm using OTS timestamping extensively as part of the Inkan key revocation and replacement system. The above is what I've concluded is needed after a lot of experimenting.

nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqzqc5dhxz0rp7l2x2unvaelt5rcyprey0qkgltxm224gwt0uzshlqcfszw87

原始 JSON

{
  "kind": 1,
  "id": "ec35aee7b9a3ef7f4d98a2a0910288c79d8d6a54e13bdf41a71ed2a83c41111f",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1774136658,
  "tags": [
    [
      "q",
      "628db984f187df5195c9b3b9fae83c1023c91e0b23eb36d4aaa1cb7f050bfc18",
      "wss://relay.primal.net/",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "e",
      "e5b7ec9a5854b69c6d59ceea0c423d0f44d0996dcccd00764c174d8aa9e0162b",
      "wss://nos.lol/",
      "root",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "p",
      "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451"
    ],
    [
      "p",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ]
  ],
  "content": "If NIP-3 is going to change, the most important thing to incorporate into the updated specification is that the item that gets timestamped must include both the *event_id* and the *signature* of the target event. I think including the signature is quite crucial. See below for discussion with nostr:npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds about this issue.\n\nThe ideal shape for an OTS event should also include something like a p-tag for the pubkey of the target event, a c-tag for the created_at time of the target event, a b-tag for the bitcoin block that anchors the timestamp, and a t-tag for the time of that bitcoin block.\n\nI'm using OTS timestamping extensively as part of the Inkan key revocation and replacement system. The above is what I've concluded is needed after a lot of experimenting.\n\n\nnostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqzqc5dhxz0rp7l2x2unvaelt5rcyprey0qkgltxm224gwt0uzshlqcfszw87",
  "sig": "4be3a3629ccd25af154b8455673a7b7cc8194385eac26e079898dc701290ae52db66d71126abf145a8490f2b17d2a382cb29501dedaf5f20217b78661fd823aa"
}