DNN: Decentralized Naming Network

A Bitcoin-anchored naming system for nostr and the web.

- Doesn't bloat Bitcoin (no data added to it).

- Not a blockchain / there's no shitcoin.

- Permissionless.

- Censorship-resistant.

- Scalable.

- Cheap / no recurring payment.

- Have whatever name you want and change it whenever you want.

- Human-readable & human-memorable ID/address/true-name.

- A lot of secondary-effect solutions and benefits that come out of this.

Here's the slave ICANN site for it:

https://icannot.xyz/

(^ links to the readme to read about it, along with the NIP-DN and node policy)

Tell me what you think. This is a draft and might not go anywhere.

Decided to share it with the public early, even before talks with people.

Ask any questions or share any concerns or criticisms you may have.

If this turns out to be a proper solution, then I'd continue developing it, assuming I'd have funds for it, or if devs come along to help develop it.

https://video.nostr.build/ce76b435f360425f24ec98faeb037527bc33af90e453511c67b8ca813f62b14c.mp4

Reply to this note

Please Login to reply.

Discussion

So every name has to correspond with a bitcoin (self transfer) transaction? That seems limited in scale

Can you elaborate?

From the readme

4. Publish a kind:60600 event, referencing the above and including a Bitcoin self-transfer as proof.

Yes, but what I meant to ask is if you can elaborate on how that limits the solution at scale

Well let's say it catches on and is on track to replace the 350 million or so entries in ICANN. At bitcoin's speed of roughly 7 transactions per second that would take like 1.5 years of this to the exclusion of all other transactions

Ah, ok.

DNN doesn't have to replace ICANN, but it can with time assuming people like it. What you said in my eyes is good news actually. In realistic terms, people won't hop on to DNN at the same time, it'll be gradual, slowly but surely people would get a DNN name/ID (if I had to guess when it would have above 50% of the market, it'll probably be 25 to 50 years later).

Though let's assume this scenario where every renter of those 350 million domains suddenly wanted to have their name on DNN, then 2 years or less of waiting (heck, 3 years why not), to move the whole of this massive legacy system to a new one, in one go, in that time frame, and then everything is done? That's fantastic and fast actually.

Would be nicer if it could be done with opentimestamp or something

I've modified the NIP-ND, specifically kind:61600 and kind:62600, where it now does what I mentioned previously. This means that after one acquires an ID, they can have multiple names under it that lead to different servers/sites, without needing to register a new ID.

Example:

- You've managed to acquire the ID nABCPoolDog.

- By default, it goes to the first IP, and the first/primary name (found in kind:61600). So "desiredName.nABCPoolDog" leads to the same server as "nABCPoolDog" (note: nothing is case-sensitive).

- However, after setup, otherName1.nABCPoolDog leads to a different server/website, otherName2.nABCPoolDog leads to a third different server/website, and so on.

It's like you bought a ".com" and you can have whatever domain you want under it. "name1.com", "name2.com", and so on, without requiring an additional Bitcoin transaction.

With that change, the protocol is now much more scalable and cheaper than before, without breaking multiple parts of it or changing its core registration/acquisition process.

With a single registration/acquisition, you can have however many domains you desire, only restricted by the file size that the DNN node operators allow in their policy.

Note:

nABCPoolDog as a social identity, like here on nostr, will resolve to itself and/or to the first/primary name only, which is equal to the npub that owns that 'nABCPoolDog'.

I like the first point