The idea behind an addressable event is that the pubkey sign...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

29730cde7f50891c983efa0143aa6fbd364a6894e7aa3520ab557d8ca39ec657

nevent

nevent1qqszjucvmel4pzgunql05q2r4fhm6dj2dz2w0234yz442lvv5w0vv4cprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcl8uweg

Kind-1 (TextNote)

2026-06-09T11:04:23Z

↳ Reply to Event not found

cca7558f59015e8bbe51f3315fb9e7eff3abf1b30b46f959b1da673bc1c361af...

The idea behind an addressable event is that the pubkey signing the event gets to have no more than one "opinion" as to what the best OTS proof for the reference event is (where "best" means the one that proves the lowest block height).

As for entire OTS proofs being held inside Nostr events, this does not really conflict with the idea that proofs can also be held somewhere else in some other form. It's just one form of holding the proofs that is pretty natural in the context of Nostr, given that relays are readily available. So I think it should be made available as an option, just a piece of infrastructure that one can choose to use or not.

Raw JSON

{
  "kind": 1,
  "id": "29730cde7f50891c983efa0143aa6fbd364a6894e7aa3520ab557d8ca39ec657",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1781003063,
  "tags": [
    [
      "e",
      "3112043f4340558caf037893ccc95861aa421c3af9ef3c0076703e622610c57e",
      "wss://nos.lol/",
      "root",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "e",
      "cca7558f59015e8bbe51f3315fb9e7eff3abf1b30b46f959b1da673bc1c361af",
      "wss://relay.primal.net/",
      "reply",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "p",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "p",
      "e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
    ],
    [
      "p",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ],
    [
      "p",
      "ccaa58e37c99c85bc5e754028a718bd46485e5d3cb3345691ecab83c755d48cc"
    ],
    [
      "p",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ]
  ],
  "content": "The idea behind an addressable event is that the pubkey signing the event gets to have no more than one \"opinion\" as to what the best OTS proof for the reference event is (where \"best\" means the one that proves the lowest block height).\n\nAs for entire OTS proofs being held inside Nostr events, this does not really conflict with the idea that proofs can also be held somewhere else in some other form. It's just one form of holding the proofs that is pretty natural in the context of Nostr, given that relays are readily available. So I think it should be made available as an option, just a piece of infrastructure that one can choose to use or not.",
  "sig": "62165191ab00c83aebd9e9830f3a7f11e001438fe2833ec3afba8c8ea60891e230cf430b5c886a911f5b6e1cee444ae45cd3e304da27d3f74ef75d6f0dee5e10"
}