I haven't implemented DMs but actually started thinking abou...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

30e1d5db5842a32c8d25273331455684aa37167974b71b7fa7225514a92dadad

nevent

nevent1qqsrpcw4mdvy9gev35jjwve3g4tgf23hzeuhfdcm07njy4g54yk6mtgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcgpcx9s

Kind-1 (TextNote)

2026-09-07T16:44:02Z

↳ Reply to Event not found

00000025070f409c26c153445b117ec73b0fcc1f0d1a577d746bfef53971d202...

I haven't implemented DMs but actually started thinking about this recently. You'll want to treat delegatee keys like different phone numbers that belong to the master key and which the master key advertises as capable of receiving DMs. The caller decides to which delegatee they want to deliver the DM, and Inkan permits them to verify the association of the delegatee with the master.

One interesting use of Inkan is to associate delegatee keys with specific devices that belong to the master identity. I think you may be able to use this for a double ratchet for Nostr. 👇

nostr:nevent1qvzqqqqy2upzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsqg9mux5805dcaz66df77u7lqxt8funcuqdzpxqw59kw7ty5hljvpmvjrllrj

Raw JSON

{
  "kind": 1,
  "id": "30e1d5db5842a32c8d25273331455684aa37167974b71b7fa7225514a92dadad",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788799442,
  "tags": [
    [
      "q",
      "bbe1a877d1b8e8b5a6a7dee7be032ce9e4f1c03441301d42d9de59297fc981db",
      "wss://relay.damus.io/",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "e",
      "0bb4daf107c109410d85a15391dd4961e47fa97cfc7d35f83c1a1df0bb44d531",
      "wss://nostr.mom/",
      "root",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "e",
      "00000025070f409c26c153445b117ec73b0fcc1f0d1a577d746bfef53971d202",
      "wss://relay.damus.io/",
      "reply",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ],
    [
      "p",
      "50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
    ],
    [
      "p",
      "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451"
    ],
    [
      "p",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ]
  ],
  "content": "I haven't implemented DMs but actually started thinking about this recently. You'll want to treat delegatee keys like different phone numbers that belong to the master key and which the master key advertises as capable of receiving DMs. The caller decides to which delegatee they want to deliver the DM, and Inkan permits them to verify the association of the delegatee with the master.\n\nOne interesting use of Inkan is to associate delegatee keys with specific devices that belong to the master identity. I think you may be able to use this for a double ratchet for Nostr. 👇\n\nnostr:nevent1qvzqqqqy2upzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsqg9mux5805dcaz66df77u7lqxt8funcuqdzpxqw59kw7ty5hljvpmvjrllrj",
  "sig": "67823946a2a3885f9cb935dd128af77844b4a036378c37faa444e15dc38f2c265c04f68a15abeb921abeffdf5455320eb7f5c4b8dea20f1910c59fa8c3c854db"
}