The "shooting down" of proposals on key rotation is just a c...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

2c3615f75dffda196a380407ecb2ec7c00844a0d6d1180c2ff17d19e161b922c

nevent

nevent1qqszcds47awllksedguqgplvktk8cqyyfgxk6yvqctl305v7zcdeytqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gc4jgssh

Kind-1 (TextNote)

2026-09-08T04:47:58Z

↳ Reply to Event not found

00000009ee9f36da0895ff195f4d3f1e979a8164540a8bb6a28072882d8ade91...

The "shooting down" of proposals on key rotation is just a cultural issue with Nostr. It's not a technical limitation.

This thread is an example of this. Lots of comments about how key rotation is impossible. And when I post links to a website where a functioning key rotation has actually been implemented and is in use, it's mostly just ignored. And then there are more comments on how nobody has figured our how to do key rotation. There's a lot of cognitive dissonance here.

I guess I'll just keep posting links. Here is a functioning key revocation and replacement system for Nostr, which you can start using today. 👇

nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcqyqydc5vcy4z8zk350dsykgfkrq5uc2jvzmaa9k709hq88ku90gt5qs7r4gy

Raw JSON

{
  "kind": 1,
  "id": "2c3615f75dffda196a380407ecb2ec7c00844a0d6d1180c2ff17d19e161b922c",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788842878,
  "tags": [
    [
      "q",
      "08dc51982544715a347b604b21361829cc2a4c16fbd2dbcf2dc073db857a1740",
      "wss://relay.damus.io/",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "e",
      "0bb4daf107c109410d85a15391dd4961e47fa97cfc7d35f83c1a1df0bb44d531",
      "wss://nostr.mom/",
      "root",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "e",
      "00000009ee9f36da0895ff195f4d3f1e979a8164540a8bb6a28072882d8ade91",
      "wss://nostr.mom/",
      "reply",
      "4a38463c2a75e68c24416e7720a3b3befbb0ea6872d5a04692c39e18e8f2dcac"
    ],
    [
      "p",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "p",
      "4a38463c2a75e68c24416e7720a3b3befbb0ea6872d5a04692c39e18e8f2dcac"
    ]
  ],
  "content": "The \"shooting down\" of proposals on key rotation is just a cultural issue with Nostr. It's not a technical limitation.\n\nThis thread is an example of this. Lots of comments about how key rotation is impossible. And when I post links to a website where a functioning key rotation has actually been implemented and is in use, it's mostly just ignored. And then there are more comments on how nobody has figured our how to do key rotation. There's a lot of cognitive dissonance here.\n\nI guess I'll just keep posting links. Here is a functioning key revocation and replacement system for Nostr, which you can start using today. 👇\n\nnostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcqyqydc5vcy4z8zk350dsykgfkrq5uc2jvzmaa9k709hq88ku90gt5qs7r4gy",
  "sig": "8c14eef0bb8e6aa51d559f22443e263eb4782a58102fcde8ccd072217b7ad297b0f4cc8fe38c393e30f8489f7dca5d83bf6c6d101b82402baa7ac457bcff5a40"
}