I don't agree that Inkan automatically adds to the severity ...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

81e6a1c804f267c182f04102764e78ca56c2cf8d1e774f12544b3abd88dcd2b4

nevent

nevent1qqsgre4peqz0ye7pstcyzqnkfeuv54kze7x3ua60zf2ykw4a3rwd9dqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcp9l9ln

Kind-1 (TextNote)

2026-09-09T11:12:04Z

↳ Reply to Event not found

36684ac689e7a5100b8f1ed9f8900665ba5681256e670773a671ce77156362a3...

I don't agree that Inkan automatically adds to the severity of a total loss of identity.

"[if] someone steal a main-key, there is this automated infrastructure that immediately diverts the audience towards wherever the attacker wants them"

That's precisely the same with normal Nostr keys. If someone steals your normal Nostr key, they can divert the attention of your entire audience to their own posts and other activity under the guise of your compromised identity. Same with a compromised Inkan master key. The remedial steps you can take after such a loss are the same for Inkan and normal Nostr. I don't think that there's additional severity that Inkan adds as compared to normal Nostr.

I think that the severity of a total loss depends on how much you had invested in that identity. E.g. if you make an Inkan "toy identity" on the Inkan home page, you can play around with it without investing any serious effort in it and then throw it away. It's a fully functional Inkan identity, but you wouldn't feel the loss of the master key because you haven't put much effort into it.

I should also point out that Inkan gives "normies" a feature that's to some extent analogous to a crucial functionality they are used to from legacy "platforms": the ability to reset their password.

Raw JSON

{
  "kind": 1,
  "id": "81e6a1c804f267c182f04102764e78ca56c2cf8d1e774f12544b3abd88dcd2b4",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788952324,
  "tags": [
    [
      "e",
      "3aec1cd219bede90b0706e590bb2cae9ff3b14a472019d6d6fb312cb175679db",
      "wss://relay.primal.net/",
      "root",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "e",
      "36684ac689e7a5100b8f1ed9f8900665ba5681256e670773a671ce77156362a3",
      "wss://relay.azzamo.net/",
      "reply",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "p",
      "61bf790b2094afb03495c9e136acf615be0fccc2cb95b5acfb5f6ccefe18b062"
    ],
    [
      "p",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ]
  ],
  "content": "I don't agree that Inkan automatically adds to the severity of a total loss of identity.\n\n\"[if] someone steal a main-key, there is this automated infrastructure that immediately diverts the audience towards wherever the attacker wants them\"\n\nThat's precisely the same with normal Nostr keys. If someone steals your normal Nostr key, they can divert the attention of your entire audience to their own posts and other activity under the guise of your compromised identity. Same with a compromised Inkan master key. The remedial steps you can take after such a loss are the same for Inkan and normal Nostr. I don't think that there's additional severity that Inkan adds as compared to normal Nostr.\n\nI think that the severity of a total loss depends on how much you had invested in that identity. E.g. if you make an Inkan \"toy identity\" on the Inkan home page, you can play around with it without investing any serious effort in it and then throw it away. It's a fully functional Inkan identity, but you wouldn't feel the loss of the master key because you haven't put much effort into it.\n\nI should also point out that Inkan gives \"normies\" a feature that's to some extent analogous to a crucial functionality they are used to from legacy \"platforms\": the ability to reset their password.",
  "sig": "95a9fcdafcb7d74f1400759c07b5c13cb02bb6a7e62505bf8b35039fc81bccc610ead04622ea7047809592ea68d5c9472bb5e36a04582d17247a8e6faad7dba4"
}