pull down to refresh

DNN: Decentralized Naming Network
767 sats \ 4 comments \ @freakoverseOG 24 Oct nostr
(I wasn't sure where to make this post, if it should be posted on here/nostr or on bitcoin, but decided here).
DNN, 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.
I essentially examined the issues of past attempts to eliminate reliance on ICANN and noticed their problems, and collected others' criticisms of them, which led me to develop this approach.
Here's a presentation of the idea: https://video.nostr.build/ce76b435f360425f24ec98faeb037527bc33af90e453511c67b8ca813f62b14c.mp4
Aside from that, you can read up on the README file and other files (NIP-DN and node policy) from the repo found on this slave site: https://icannot.xyz/
Would like to hear people's thoughts on it.
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.
write
preview
related posts
0 sats \ 1 reply \ @k00b 25 Oct
Interesting scheme. I was curious how it was both "anchored in the bitcoin" and not putting data on-chain which is laid out in (4):
  1. Publish a kind:61600 event with your desired name.
  2. Publish a kind:62600 event with connection data.
  3. Publish a kind:63600 event with metadata.
  4. Publish a kind:60600 event, referencing the above and including a Bitcoin self-transfer as proof.
This inversion of offchain referencing onchain rather than the reverse is not something I've seen before.
I was also curious how one can "Have whatever name you want and change it whenever you want" and it appears that that's only true if your name carries metadata about how to verify the name:
alice.n50.5 alice.b1000050.5
This can be shortened to another encoding I guess:
To improve human readability and memorability and make referencing DNN names easier, DNN supports an extra encoded format that compresses the block number and transaction position into a compact alphanumeric string.
The above example becomes:
alice.agd-abandon alice.ytj-abandon-zoo
Which is objectively more human friendly even if it's unsatisfying.
Overall I feel like I'm not able to "Have whatever name I want" but it's an interesting scheme.
reply
21 sats \ 0 replies \ @freakoverseOG OP 25 Oct
I'm basically differentiating between an "ID" and a "name", where "alice.n50.5" can be "bob.n50.5" where the change happens in nostr event kind:61600
reply
0 sats \ 1 reply \ @supratic 25 Oct
What are the alternatives you have found not satisfying your expectations that push you to build this solution?
reply
0 sats \ 0 replies \ @freakoverseOG OP 25 Oct
Most of them require running a separate blockchain that is not the most secure in comparison to Bitcoin, and most of them seem to be centralized (or at least not as decentralized), and having to deal with a currency that is not as solid as Bitcoin, and for those that have used Bitcoin, they're adding non-transactionary data and bloating bitcoin with said data where aside from being limited by their sizes, there might be a future that these loop-holes get removed.
So I basically looked at all their problems (from what I knew and from what people have mentioned), and thought, "Can there be something that doesn't have any of those issues?" and came up with this solution with those points mentioned in the OP.
From my pov, it seems like this solves all those issues, scales well, and is secured (without bloating/adding junk to Bitcoin), etc.
reply