Similar thing, my 31045s allow "not_yet_available" in the bl...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

d0cb490e0b6337a5b2c4eec2ed7c46df1a7fe4f58144ad9a80e25c1237e0ee5c

nevent

nevent1qqsdpj6fpc9kxda9ktzwashd03rd7xnlun6cz39dn2qwyhqjxlswuhqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcxqcfvr

Kind-1 (TextNote)

2026-06-07T18:25:21Z

↳ Reply to Event not found

1d298959e362d772643a23b05fb9d9b123964785eb5938da64c35452da97b2b7...

Similar thing, my 31045s allow "not_yet_available" in the block height tag, and then later the 31045 can get replaced with one that carries a complete proof.

But if I remember correctly your 1041 automatically expire after a week or so, which makes sense.

My client basically has settings in which users specify a list of pubkeys for which they want to be stewards of OTS info, and then the client automatically tries to do the work of keeping the OTS info updated for events from those pubkeys. The default setting is simply that users are stewards for OTS info for their own pubkey.

Raw JSON

{
  "kind": 1,
  "id": "d0cb490e0b6337a5b2c4eec2ed7c46df1a7fe4f58144ad9a80e25c1237e0ee5c",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1780856721,
  "tags": [
    [
      "e",
      "3112043f4340558caf037893ccc95861aa421c3af9ef3c0076703e622610c57e",
      "wss://relay.primal.net/",
      "root",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "e",
      "1d298959e362d772643a23b05fb9d9b123964785eb5938da64c35452da97b2b7",
      "wss://relay.primal.net/",
      "reply",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "p",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "p",
      "e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
    ],
    [
      "p",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ],
    [
      "p",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ]
  ],
  "content": "Similar thing, my 31045s allow \"not_yet_available\" in the block height tag, and then later the 31045 can get replaced with one that carries a complete proof. \n\nBut if I remember correctly your 1041 automatically expire after a week or so, which makes sense.\n\nMy client basically has settings in which users specify a list of pubkeys for which they want to be stewards of OTS info, and then the client automatically tries to do the work of keeping the OTS info updated for events from those pubkeys. The default setting is simply that users are stewards for OTS info for their *own* pubkey.",
  "sig": "240525a4f496be35727b7e1780aa70af116b5ec1daab3b7cebc561d8e98e46253a1331a54c61ae05a72ce4282e9a492b638ced3134ec250a08fe4d52029827a0"
}