Is there a nip for that or is it implemented only in that ap...

The Fishcake (nostr.build)

npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w

hex

002299674f7aae2a0b4c77281a6ca0a2a3bd3e2a47e951d63047f3d429c7bef6

nevent

nevent1qqsqqg5eva8h4t32pdx8w2q6djs29gaa8c4y06236ccy0u7598rmaasprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsglv2qkn5dmmuhee9cy8fywfu2rfp4xd3xy0myqg2gfvmjl9yqqrqc3pn6c

Kind-1 (TextNote)

2026-08-30T10:59:46Z

↳ Reply to inkan (npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l)

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 stora...

Is there a nip for that or is it implemented only in that app? One constraint I have is not needing to query any external services during authorization. If we have to do some tracking of key revocations or anything like that, then it’ll be impossible for us to accommodate. I haven’t looked at any sample code yet, so just asking for now

Raw JSON

{
  "kind": 1,
  "id": "002299674f7aae2a0b4c77281a6ca0a2a3bd3e2a47e951d63047f3d429c7bef6",
  "pubkey": "8fb140b4e8ddef97ce4b821d247278a1a4353362623f64021484b372f948000c",
  "created_at": 1788087586,
  "tags": [
    [
      "e",
      "a764d7f75d71722b7fcac7dd2fde347e227b075d9289dd9ccb45379761a11f22",
      "wss://nos.lol/",
      "root",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "e",
      "3013100487af32617e475853933571ebe882c918998e2076085b871f5c36d948",
      "wss://premium.primal.net/",
      "reply",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "p",
      "e28ef176cd7618a8cc0147570d88ff76bb252bbdd2252f99eda3fe019f673730"
    ],
    [
      "p",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "p",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ]
  ],
  "content": "Is there a nip for that or is it implemented only in that app? One constraint I have is not needing to query any external services during authorization. If we have to do some tracking of key revocations or anything like that, then it’ll be impossible for us to accommodate. I haven’t looked at any sample code yet, so just asking for now",
  "sig": "f6bd8ae792f7051edfa772ff355efd4925ee5933feabd0f2fb19fc5e76d9670b0cf3875ec31d6aa2e3b9d1fcafe33c5355665898b7889bc0bac41bc0163df871"
}