I think that's most likely the issue I pointed out in the no...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

1e0b23875b20ba18f5d0b86e7155cfa3d1faa99c319b117cd497e3c5b1ed3803

nevent

nevent1qqspuzersadjpwsc7hgtsmn32h8685064xwrrxc30n2f0c79k8knsqcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gchxsrdp

Kind-1 (TextNote)

2026-08-19T15:36:39Z

↳ Reply to Event not found

6bfc8a5aad1668ea8de1f565422d4cbfe800656c2065927d055d148aed2ed101...

I think that's most likely the issue I pointed out in the note below.

You have probably been posting from a client other than https://www.inkan.cc which means that you didn't automatically publish 31045 OTS timestamps for your events to the Inkan relay (only the Inkan client takes care of this automatic publication). This means that Inkan now cannot find these timestamps for your events on the relay and thus treats your events as invalid.

You should be able to correct this by logging into the Inkan client and making sure that your signer extension approves the signing of 31045 events. You should then probably stay logged in for some time since the client's catching up on the publication of the missing events might take a while. The timestamps for your events exist on the timestamping server, your Inkan client just needs to catch up with publishing them to the relay as 31045 events.

nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpq0s68vaad834p7c9jqj8sppfge4wj0qx0dqmfdrn693gucta8g0xsuxw0fn

Raw JSON

{
  "kind": 1,
  "id": "1e0b23875b20ba18f5d0b86e7155cfa3d1faa99c319b117cd497e3c5b1ed3803",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1787153799,
  "tags": [
    [
      "q",
      "7c347677ad3c6a1f60b2048f008528cd5d2780cf6836968e7a2c51cc2fa743cd",
      "wss://relay.damus.io/",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "e",
      "6bfc8a5aad1668ea8de1f565422d4cbfe800656c2065927d055d148aed2ed101",
      "wss://relay.primal.net/",
      "root",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "p",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ]
  ],
  "content": "I think that's most likely the issue I pointed out in the note below.\n\nYou have probably been posting from a client other than https://www.inkan.cc, which means that you didn't automatically publish 31045 OTS timestamps for your events to the Inkan relay (only the Inkan client takes care of this automatic publication). This means that Inkan now cannot find these timestamps for your events on the relay and thus treats your events as invalid.\n\nYou should be able to correct this by logging into the Inkan client and making sure that your signer extension approves the signing of 31045 events. You should then probably stay logged in for some time since the client's catching up on the publication of the missing events might take a while. The timestamps for your events exist on the timestamping server, your Inkan client just needs to catch up with publishing them to the relay as 31045 events.\n\n\nnostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpq0s68vaad834p7c9jqj8sppfge4wj0qx0dqmfdrn693gucta8g0xsuxw0fn",
  "sig": "0f06044415e4b5f0ac7dd8d15c966fbac8e4b3b5c2102f6bf8f9856889bb2d590f51fe3948830625cefb2ae6d80010b1b831aee5ee6f5b7d3fb6f40d163f88b8"
}