I looked at the github page and as far as I can tell DNN is meant to be a substitute for DNS identifiers?
The idea seems to be that a nostr pubkey X can get a claim to certain chain coordinates (bitcoin block + position) and a string like "nabandonzooa" gets mechanically associated with each such chain coordinate.
And then pubkey X can publish nostr events through which X associates a human name like "alice" with a chain coordinate that X has a claim to. So for example X can publish nostr events through which X declares "I associate 'alice' with the chain coordinate 'nabandonzooa'."
It looks like nothing prevents X from publishing nostr events on relay A through which it associates "alice" with "nabandonzooa," and nostr events on relay B through which it associates "john" with "nabandonzooa."
Now a full node can discover *all* of the chain coordinates that have been claimed by pubkeys under this scheme, and it could for example identify the most recent chain coordinate C that was claimed by pubkey X, say the one whose string is "nebuchadnezzar". Then one can look at X's nostr events and find an event on relay A showing that X has associated "alice" with "nebuchadnezzar." Of course one can't be sure that there isn't some other event on some unknown relay B through which X has associated "john" with "nebuchadnezzar."
The result seems similar to searching for kind-0 profiles published by pubkey X. One might for example find a profile event signed by X with the profile name "alice" on relay A and choose to display that in a client, but of course one cannot be sure that there is no other profile event signed by X on some other relay B that shows "john" as the profile name.
I'm not sure yet what exactly this system is trying to add.
inkan
npub16x…56z6l
2026-10-15 05:51:52 UTC
in reply to nevent1q…40zq
Author Public Key
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6lPublished at
2026-10-15 05:51:52 UTCEvent JSON
{
"id": "164323eaa4f4a4ba0297aad9c44908dd992213e98776d175f87ada9dbca27049",
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"created_at": 1792043512,
"kind": 1,
"tags": [
[
"e",
"f9d09a5cd4b0a5811dee6dd306295b71388cc684bd04514f43bf12f2262438dd",
"wss://relay.damus.io/",
"root",
"d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
],
[
"e",
"5f284fc42e5552447cc37dd496b915e4f4053a5ac3d396e67aaf6845c8e8cf89",
"wss://relay.inkan.cc/",
"reply",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
],
[
"p",
"ee6ea13ab9fe5c4a68eaf9b1a34fe014a66b40117c50ee2a614f4cda959b6e74"
],
[
"p",
"e09eb3c8af93b5d33aabfeea594ea73e2dabc3aaee5c645ffa35675d68572324"
],
[
"p",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
]
],
"content": "I looked at the github page and as far as I can tell DNN is meant to be a substitute for DNS identifiers?\n\nThe idea seems to be that a nostr pubkey X can get a claim to certain chain coordinates (bitcoin block + position) and a string like \"nabandonzooa\" gets mechanically associated with each such chain coordinate.\n\nAnd then pubkey X can publish nostr events through which X associates a human name like \"alice\" with a chain coordinate that X has a claim to. So for example X can publish nostr events through which X declares \"I associate 'alice' with the chain coordinate 'nabandonzooa'.\"\n\nIt looks like nothing prevents X from publishing nostr events on relay A through which it associates \"alice\" with \"nabandonzooa,\" and nostr events on relay B through which it associates \"john\" with \"nabandonzooa.\"\n\nNow a full node can discover *all* of the chain coordinates that have been claimed by pubkeys under this scheme, and it could for example identify the most recent chain coordinate C that was claimed by pubkey X, say the one whose string is \"nebuchadnezzar\". Then one can look at X's nostr events and find an event on relay A showing that X has associated \"alice\" with \"nebuchadnezzar.\" Of course one can't be sure that there isn't some other event on some unknown relay B through which X has associated \"john\" with \"nebuchadnezzar.\"\n\nThe result seems similar to searching for kind-0 profiles published by pubkey X. One might for example find a profile event signed by X with the profile name \"alice\" on relay A and choose to display that in a client, but of course one cannot be sure that there is no other profile event signed by X on some other relay B that shows \"john\" as the profile name.\n\nI'm not sure yet what exactly this system is trying to add.",
"sig": "17eb4d5544498cbb69dcc78f50adbcbd935404a44a23d0d51a4a46cda2e693ed0242277c875c842ef7997e24654df4b7c7d4a23b5a323641b9484f64912d602f"
}