If you follow my current signer key A and I replace with a d...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

778cc9d19209f1a1861c8abf459f3b2f24ccd4c51ea04a50e2975ed637ab9e27

nevent

nevent1qqs80rxf6xfqnudpscwg4069nuaj7fxv6nz3agz22r3fwhkkx74eufcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gc99mwzg

Kind-1 (TextNote)

2026-09-07T18:49:16Z

↳ 回复 事件不存在

00000069a58d05e04ac60fa1e61289d98cbde4261e32014aa823dda17bcb9652...

If you follow my current signer key A and I replace with a different signer key B, you will need to separately start following my signer key B to see its posts on Amethyst in your following timeline.

But if you follow my delegator key X which delegated to signer A and later replaced it with signer key B, then the Inkan client will show you all of X's events, both those signed by A and those signed by B, under X's profile.

In the meantime, nothing in the regular Nostr protocol gets broken. From the regular protocol's point of view, A and B are just completely normal Nostr keys. And X is also a normal Nostr key, which will show up in Amethyst as having no events whatsoever. Inkan does not displace or interfere with the current protocol.

To see some key rotations, you can look at the profile of this pubkey:

https://www.inkan.cc/users/npub1nqghyutxtxmf5r4mwys5xvp5upv8hv7z3a2ywpmnynwaetja7x0snq68nf

You can for example pick events from each of May 22, May 28 and June 20. If you click on "View raw event" for each of these, you'll see the different delegatee pubkeys that signed these.

原始 JSON

{
  "kind": 1,
  "id": "778cc9d19209f1a1861c8abf459f3b2f24ccd4c51ea04a50e2975ed637ab9e27",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788806956,
  "tags": [
    [
      "e",
      "0bb4daf107c109410d85a15391dd4961e47fa97cfc7d35f83c1a1df0bb44d531",
      "wss://nostr.mom/",
      "root",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "e",
      "00000069a58d05e04ac60fa1e61289d98cbde4261e32014aa823dda17bcb9652",
      "wss://relay.damus.io/",
      "reply",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ],
    [
      "p",
      "4a38463c2a75e68c24416e7720a3b3befbb0ea6872d5a04692c39e18e8f2dcac"
    ],
    [
      "p",
      "576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
    ],
    [
      "p",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
    ],
    [
      "p",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "p",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ]
  ],
  "content": "If you follow my current signer key A and I replace with a different signer key B, you will need to separately start following my signer key B to see its posts on Amethyst in your following timeline.\n\nBut if you follow my delegator key X which delegated to signer A and later replaced it with signer key B, then the *Inkan* client will show you all of X's events, both those signed by A and those signed by B, under X's profile.\n\nIn the meantime, nothing in the regular Nostr protocol gets broken. From the regular protocol's point of view, A and B are just completely normal Nostr keys. And X is also a normal Nostr key, which will show up in Amethyst as having no events whatsoever. Inkan does not displace or interfere with the current protocol.\n\nTo see some key rotations, you can look at the profile of this pubkey:\n\nhttps://www.inkan.cc/users/npub1nqghyutxtxmf5r4mwys5xvp5upv8hv7z3a2ywpmnynwaetja7x0snq68nf\n\nYou can for example pick events from each of May 22, May 28 and June 20. If you click on \"View raw event\" for each of these, you'll see the different delegatee pubkeys that signed these.",
  "sig": "67b293b7dc331f98fc80230c93c3b589a063ecb1b87ee7921d3289285621883a80b79387657de61e160b4c061d1756a66aabf275107d4f8cabcd661b73577866"
}