It's OpenTimestamps. https://opentimestamps.org/

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

ac05906d5d2fa47ca802841a97d4545edb6cc942386fb42c3c252367c677bead

nevent

nevent1qqs2cpvsd4wjlfru4qpggx5h6329akmve9prsma59s7z2gm8cemmatgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcl6zvez

Kind-1 (TextNote)

2026-06-11T17:54:52Z

↳ 回复 事件不存在

97f92452df9dc38c90dd6e523ce38bd726541e80b5da3d393b5fbdcc6188d76f...

It's OpenTimestamps. https://opentimestamps.org/

The created_at timestamps that are included in Nostr events are self-declared and can be faked. Instead of relying on these, Nostr events can get objective timestamps that are recorded on Bitcoin, proving that the event must have existed at the time of some Bitcoin block. To do this correctly, it's necessary to timestamp a concatenation of the event_id and the event's signature. These timestamps can be created efficiently for large numbers of events using Merkle trees, and it's pretty quick and easy for clients to verify that an event has a valid Bitcoin timestamp.

For Project Gutenberg, timestamping these books on Bitcoin would prove that they existed in the exact form in which you recorded them as of, say, June 11, 2026. This would give people the ability to confirm that these books have not been altered since that time. There have been attempts to alter classic works to fit current sensibilities, and there could conceivably be attempts to either remove the unaltered versions from the internet altogether or to obfuscate what the original version was.

It's possible that someone has already timestamped the Project Gutenberg texts, I'm not sure. But what you're doing seems like an opportunity to do so.

原始 JSON

{
  "kind": 1,
  "id": "ac05906d5d2fa47ca802841a97d4545edb6cc942386fb42c3c252367c677bead",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1781200492,
  "tags": [
    [
      "e",
      "d88cc23dd4a78355c6b9f1085d6c58b6a4f82f884631758b7ad80b79bb1aee86",
      "wss://theforest.nostr1.com/",
      "root",
      "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
    ],
    [
      "e",
      "97f92452df9dc38c90dd6e523ce38bd726541e80b5da3d393b5fbdcc6188d76f",
      "wss://nos.lol/",
      "reply",
      "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
    ],
    [
      "p",
      "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
    ]
  ],
  "content": "It's OpenTimestamps. https://opentimestamps.org/\n\nThe created_at timestamps that are included in Nostr events are self-declared and can be faked. Instead of relying on these, Nostr events can get objective timestamps that are recorded on Bitcoin, proving that the event must have existed at the time of some Bitcoin block. To do this correctly, it's necessary to timestamp a concatenation of the event_id and the event's signature. These timestamps can be created efficiently for large numbers of events using Merkle trees, and it's pretty quick and easy for clients to verify that an event has a valid Bitcoin timestamp.\n\nFor Project Gutenberg, timestamping these books on Bitcoin would prove that they existed in the exact form in which you recorded them as of, say, June 11, 2026. This would give people the ability to confirm that these books have not been altered since that time. There have been attempts to alter classic works to fit current sensibilities, and there could conceivably be attempts to either remove the unaltered versions from the internet altogether or to obfuscate what the original version was. \n\nIt's possible that someone has already timestamped the Project Gutenberg texts, I'm not sure. But what you're doing seems like an opportunity to do so.",
  "sig": "2701a6c461a4c49f8d60acb822415841309417a324b1d8449dc4ad0a9ff53445cd432c87e2d85206cbb20e548b857dd61ed55b947cae9b55ce42b06054da6219"
}