I just want to point out again that we have a fully function...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

a38350cd88233aadb1aa0ba41425bdacaa6ad9da70735b66ef20fc2928f05e16

nevent

nevent1qqs28q6sekyzxw4dkx4qhfq5yk76e2n2m8d8qu6mvmhjplpf9rc9u9sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gc8qanl4

Kind-1 (TextNote)

2026-09-08T04:31:20Z

↳ Reply to cloud fodder (npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h)

Hard to get everyone to adopt key rotation yeah.. PGP is the only thing that sort-of has built-in rotation, but does it really? It's just a new key, ...

I just want to point out again that we have a fully functioning key revocation and replacement system in Nostr. I've been using it every day for months now.

You can literally just head over to https://www.inkan.cc and create an identity that can delegate signing authority to delegatee keys and revoke it when these keys are compromised.

This enables cold storage identities for Nostr. If you want to see one of these identities in action, here is an example:

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

And here is the draft NIP that goes along with the reference implementation:

nostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnvv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsq2rrdakxgttnw3hhyct8v5kkjer9de6xjarfv4ej6en0wgkkummnw3ez6ce4dccrzcgwghxg7

Raw JSON

{
  "kind": 1,
  "id": "a38350cd88233aadb1aa0ba41425bdacaa6ad9da70735b66ef20fc2928f05e16",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788841880,
  "tags": [
    [
      "q",
      "30023:d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23:cold-storage-identities-for-nostr-c5n01a",
      "wss://nostr.land/"
    ],
    [
      "e",
      "0bb4daf107c109410d85a15391dd4961e47fa97cfc7d35f83c1a1df0bb44d531",
      "wss://nostr.mom/",
      "root",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "e",
      "c0fef49f855c89414998ee2dc1241a497d12e5aafc6ab49346d0732a6df6f1fe",
      "wss://nos.lol/",
      "reply",
      "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
    ],
    [
      "p",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "p",
      "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451"
    ],
    [
      "p",
      "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
    ]
  ],
  "content": "I just want to point out again that we have a fully functioning key revocation and replacement system in Nostr. I've been using it every day for months now.\n\nYou can literally just head over to https://www.inkan.cc and create an identity that can delegate signing authority to delegatee keys and revoke it when these keys are compromised.\n\nThis enables cold storage identities for Nostr. If you want to see one of these identities in action, here is an example:\n\nhttps://www.inkan.cc/users/npub10ukg94kvrvk4qqr3482zdekfsuaw2x56wa899mnpkxqwfxl6dlkqrux0x9\n\nAnd here is the draft NIP that goes along with the reference implementation:\n\nnostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnvv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsq2rrdakxgttnw3hhyct8v5kkjer9de6xjarfv4ej6en0wgkkummnw3ez6ce4dccrzcgwghxg7",
  "sig": "079d9f3fb2ebd943addc3ce5542b4555da227282a8b92615d6f4f5c578d12740b78d781d0508dc8bf212fb878797d681fdeff78581fa5f8506bc67284d85681a"
}