Inkan displays exactly the same profile picture for my signe...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

0694122123541b9eb937099b0074ed293bda2d813be464463deedb819b19accf

nevent

nevent1qqsqd9qjyy34gxu7hymsnxcqwnkjjw769kqnherygc77akupnvv6encprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcf7zujk

Kind-1 (TextNote)

2026-09-07T17:53:21Z

↳ 回复 事件不存在

00000043d8de99731ad6dedf6782b0009f65d5cbb70d8afc522dd629d05143c6...

Inkan displays exactly the same profile picture for my signer key as all other Nostr apps do. Here it is:

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

At the same time, the posts I am making are also getting attributed to my master identity, which you can see here:

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

There is nothing nefarious or destructive about it. You can literally delegate down from a master key to your regular Nostr key and keep using your regular Nostr key as usual across the Nostr ecosystem. That's what I'm doing right now.

You'll just have gained the benefit of a master identity which can, in case your current Nostr key gets compromised, revoke it and replace it with a new one.

原始 JSON

{
  "kind": 1,
  "id": "0694122123541b9eb937099b0074ed293bda2d813be464463deedb819b19accf",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788803601,
  "tags": [
    [
      "e",
      "0bb4daf107c109410d85a15391dd4961e47fa97cfc7d35f83c1a1df0bb44d531",
      "wss://nostr.mom/",
      "root",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "e",
      "00000043d8de99731ad6dedf6782b0009f65d5cbb70d8afc522dd629d05143c6",
      "wss://nostr.mom/",
      "reply",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ],
    [
      "p",
      "4a38463c2a75e68c24416e7720a3b3befbb0ea6872d5a04692c39e18e8f2dcac"
    ],
    [
      "p",
      "576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
    ],
    [
      "p",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
    ],
    [
      "p",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "p",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ]
  ],
  "content": "Inkan displays exactly the same profile picture for my signer key as all other Nostr apps do. Here it is:\n\nhttps://www.inkan.cc/users/npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l\n\nAt the same time, the posts I am making are also getting attributed to my master identity, which you can see here:\n\nhttps://www.inkan.cc/users/npub10ukg94kvrvk4qqr3482zdekfsuaw2x56wa899mnpkxqwfxl6dlkqrux0x9\n\nThere is nothing nefarious or destructive about it. You can literally delegate down from a master key to your regular Nostr key and keep using your regular Nostr key as usual across the Nostr ecosystem. That's what I'm doing right now.\n\nYou'll just have gained the benefit of a master identity which can, in case your current Nostr key gets compromised, revoke it and replace it with a new one.",
  "sig": "3d6d79c4a25774c679669207bbf040a865250a51eecc39bd0764aaae059f03f576d36d99b8ca84b3547c912335513a30cd27389c2f8182778d76df05c807b6a1"
}