I agree DNN doesn't seem to compete with inkan. I first was trying to think of it as a complement to inkan, but that's actually a bit tricky once one tries to think through the details.
One question is which inkan key should get to have a chain coordinate and then associate human-readable names with that coordinate. Should it be the master key or the signer key?
It seems like it shouldn't be the master key because in DNN the relevant key must sign a bunch of stuff, and the master key shouldn't be in the business of signing anything, let alone signing nostr events.
And as for the signer key, inkan thinks of that as ephemeral and disposable, so it's not clear why one would want to go through the trouble of giving it some kind of chain-anchored identifier.
I may not yet be fully understanding DNN though, maybe I'm getting it wrong.
By the way, nip-05 works perfectly fine as a complement to inkan, both master key and signer key can have nip-5 DNS based identifiers if they want them.
inkan
npub16x…56z6l
2026-10-15 12:49:08 UTC
in reply to nevent1q…cl69
Author Public Key
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6lPublished at
2026-10-15 12:49:08 UTCEvent JSON
{
"id": "e5d00232f90d3942807accb9b1b359aab671ff6a1e0e796f4662d4a5e796a61b",
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"created_at": 1792068548,
"kind": 1,
"tags": [
[
"e",
"f9d09a5cd4b0a5811dee6dd306295b71388cc684bd04514f43bf12f2262438dd",
"wss://relay.damus.io/",
"root",
"d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
],
[
"e",
"ae3967ce8868de06c444bdd0d87919a3f474d15717667989dfb6ea7bfc56a4df",
"wss://nos.lol/",
"reply",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
],
[
"p",
"ee6ea13ab9fe5c4a68eaf9b1a34fe014a66b40117c50ee2a614f4cda959b6e74"
],
[
"p",
"e09eb3c8af93b5d33aabfeea594ea73e2dabc3aaee5c645ffa35675d68572324"
],
[
"p",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
]
],
"content": "I agree DNN doesn't seem to compete with inkan. I first was trying to think of it as a complement to inkan, but that's actually a bit tricky once one tries to think through the details.\n\nOne question is which inkan key should get to have a chain coordinate and then associate human-readable names with that coordinate. Should it be the master key or the signer key?\n\nIt seems like it shouldn't be the master key because in DNN the relevant key must sign a bunch of stuff, and the master key shouldn't be in the business of signing anything, let alone signing nostr events.\n\nAnd as for the signer key, inkan thinks of that as ephemeral and disposable, so it's not clear why one would want to go through the trouble of giving it some kind of chain-anchored identifier.\n\nI may not yet be fully understanding DNN though, maybe I'm getting it wrong. \n\nBy the way, nip-05 works perfectly fine as a complement to inkan, both master key and signer key can have nip-5 DNS based identifiers if they want them.",
"sig": "e890837f32206e2081b48f694966765a6c8dd0d1ba4727f35221ac6e679d54222174bc5b71c44cf9e8dcbeca03b4ad907e8d3f283d5279bf922c3bd55b30aade"
}