Sure, the idea is that Inkan splits the key that secures you...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

3013100487af32617e475853933571ebe882c918998e2076085b871f5c36d948

nevent

nevent1qqsrqycsqjr67vnp0er4s5unx4c7h6yzeyvfnr3qwcy9hpcltsmdjjqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcucvzwh

Kind-1 (TextNote)

2026-08-30T10:52:16Z

↳ 回复 事件不存在

508b6cd06a50d0f86b7f8174be11f8b7db1980a4cb6dc6c9d660941e0e56d368...

Sure, the idea is that Inkan splits the key that secures your identity from the key you use for everyday signing. The identity key stays in cold storage and delegates to the hot signer.

You can see meta’s setup by logging into https://www.inkan.cc with NIP-7. It should show a welcome popup with identities you can follow, including meta’s master identity (i.e. nostr:npub1u280zakdwcv23nqpgatsmz8lw6aj22aa6gjjlx0d50lqr8m8xucq7kf93q). If you follow that and then open its profile, you can see its notes and interact with it.

For nostr.build, “supporting” it probably means that when someone authenticates, you check whether the key that signed the authentication is acting on behalf of a master identity, and if so attribute the login/storage account/action to that master identity. Then if the signer is later revoked and replaced, nostr.build can automatically recognize the replacement signer as acting for the same continuous identity. And when you need a historical record of actions attributable to an identity, you can use OTS to make it provable later that the action happened during a period when the on-chain delegation was live.

Here's a NIP with more detailed specs👇

nostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgnwaehxw309ahkvenrdpskjm3wwp6kytcq9p3k7mry94ehgmmjv9nk2ttfv3jkuarfw35k2uedvehhyttwdaehgu3dvv6kuvp3vyxuud8n

原始 JSON

{
  "kind": 1,
  "id": "3013100487af32617e475853933571ebe882c918998e2076085b871f5c36d948",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788087136,
  "tags": [
    [
      "q",
      "30023:d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23:cold-storage-identities-for-nostr-c5n01a",
      "wss://relay.damus.io/"
    ],
    [
      "e",
      "a764d7f75d71722b7fcac7dd2fde347e227b075d9289dd9ccb45379761a11f22",
      "wss://nos.lol/",
      "root",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "e",
      "508b6cd06a50d0f86b7f8174be11f8b7db1980a4cb6dc6c9d660941e0e56d368",
      "wss://relay.damus.io/",
      "reply",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "p",
      "e28ef176cd7618a8cc0147570d88ff76bb252bbdd2252f99eda3fe019f673730"
    ],
    [
      "p",
      "8fb140b4e8ddef97ce4b821d247278a1a4353362623f64021484b372f948000c"
    ],
    [
      "p",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ]
  ],
  "content": "Sure, the idea is that Inkan splits the key that secures your identity from the key you use for everyday signing. The identity key stays in cold storage and delegates to the hot signer. \n\nYou can see meta’s setup by logging into https://www.inkan.cc with NIP-7. It should show a welcome popup with identities you can follow, including meta’s master identity (i.e. nostr:npub1u280zakdwcv23nqpgatsmz8lw6aj22aa6gjjlx0d50lqr8m8xucq7kf93q). If you follow that and then open its profile, you can see its notes and interact with it.\n\nFor nostr.build, “supporting” it probably means that when someone authenticates, you check whether the key that signed the authentication is acting on behalf of a master identity, and if so attribute the login/storage account/action to that master identity. Then if the signer is later revoked and replaced, nostr.build can automatically recognize the replacement signer as acting for the same continuous identity. And when you need a historical record of actions attributable to an identity, you can use OTS to make it provable later that the action happened during a period when the on-chain delegation was live.\n\nHere's a NIP with more detailed specs👇\n\nnostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgnwaehxw309ahkvenrdpskjm3wwp6kytcq9p3k7mry94ehgmmjv9nk2ttfv3jkuarfw35k2uedvehhyttwdaehgu3dvv6kuvp3vyxuud8n",
  "sig": "7b7082e4cc91c64c8d4805a2012d7439dbbff9f06c141e6937d925719d9a320d101cb69c2fcfb875a330b44c504f920f6561de3ee1f8f47138bc369ad429e10a"
}