DNN node code up:

GitHub

GitHub - Freakoverse/dnn-node

Contribute to Freakoverse/dnn-node development by creating an account on GitHub.

(check the DEPLOYMENT.md for installation on a linux server) Here's a quick video guide to installing one on a linux server: It's probably rough af and messy, but it's better to put something out there to play around with and improve as time goes on. (I'd honestly want to refactoring everything from the start, but that'd waste a lot of time and not having something out there for others to check isn't a good thing imo) You can read about the DNN project (read me and node-policy) and its NIPs (specifically NIP-DN) here:

Gitea

DNN

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

Couldn't be at #soveng unfortunately for SEC-06 (Identity) and SEC-07 (Network, ICANN DNS/IANA), this project pretty much fits for both cohorts. Identity & Signers (SEC-06): I made a desktop signer, DENOS, that's basically the user's nostr identity manager, that's also a wallet manager (eCash, focusing on nutzap management, and native bitcoin with both native segwit and taproot for two different purposes, DNN ID/TLD acquisition & management, local signing flow and a username/password sign-in flow, and later down the line I'd add what I'm calling Nostr Silent Payments (multi-currency, Bitcoin multisig but with good/clear UX, and a merchant e-commerce POS system (that includes traditional fiat payments). When a new user comes and generates a nostr keypair, they don't have to do anything else aside from that and you can immediatly send them eCash (nutzap focused, so no heavy token management), native bitcoin, or (later) other crypto and their tokens. And if they grab a DNN ID, aside from turning their npub (63 chars of gibberish) into a human-readable/memorable/usable/locally-meaningful ID (8-16 chars), it would also decently add to their WoT score from day 0. The Network Stack (SEC-07): There's a lot here, but focused on the ICANN-DNS problem as well as the Certificate Authority problem. With DNN, you can now have https://example.nabandonaread or https://example.naboutzook , where you acquire a Top-Level Domain (TLD) by sending yourself bitcoin from your bitcoin address that was derived from your npub and publishing a few events (DENOS has this function / as easy as it can be), and after acquring a TLD, you can have many domains at no extra cost. Forever yours, no requiring payments, no auctions, no fomo, and no trading, as simple and as fast and as cost-effect as it can be, and scales well (and it doesn't add anything to Bitcoin). SSL/TLS doesn't require CA as well, the cert would be self-signed (still secure) and you can put a thousand year validity if you want (set and forget). It should also be prepped (i hope, didn't do much testing on this part) for a Tollgate and FIPS future. Other: DNN solves other problems as well, secondary-effect benefits: - Nostr relay discovery problem (solves missing posts/messages, etc) - Relay centralization (no need to post or read from popular relays) - Impersonations (easily identify the correct person to follow) - Long event addresses (shorten event post from 150-260 chars to 18-26 chars) - Unfamiliar login flow (bringing back traditional username/password login flow, but evovled) - More Hit me up with any questions/feedback/topics, publically or privately, text or call (or in VRC, that would be fun y not x3) about any of this, especially if you want to implement DNN support in your nostr client (I forked Jumble and added support for it there, including some of the other benefits/NIPs like username/password login, local signer login, ID resolution, event addressing shortening, but forgot to add node query for user relay to be utilized so perhaps later), check it out:

Jumble

A user-friendly Nostr client for exploring relay feeds

#nostr #DNS #ICANN

Had an interesting discussion with another person about bloat/spam on bitcoin, we were pretty much on the same page, aside from my DNS solution with DNN. Even though DNN doesn't add anything to Bitcoin (no op_return data, no exploitation of witness data / taproot, zero), no writes, where it only reads from Bitcoin as users do a simple self-transfer (bitcoin address A sends to the send bitcoin address A), I could not comprehend the presented issue of: 'There's now an incentive for people to do self transfers, and at scale this would result in bloat in bitcoin not for its intended purpose of sending money from A to B.' (paraphrasing) I couldn't comprehend the presented or perceived issue because: 1. It is sending A to B ('B' being 'A' itself) 2. It doesn't add anything, no bloat 3. Even if a full block or blocks were about these self-transfers, they are legit and clean (no non-transactional data / zero) The gentleman I was discussing it with see DNN as a bigger threat than Ordinals, which came to me as a surprise considering I myself am against it, and don't mind also if op_return was zero, and that's why I made the DNN the way it is now. My best attempt at coming to an understanding is that because the reason/incentive isn't about sending money from A to B just so that B can have the money, then this shouldn't be socially pushed to become mainstream because if it catches on and many people start doing self-transfers, it'll bloat bitcoin blocks with these self-transfer type of transactions. But even then, my thought was "So... because the reason/incentive for sending a transaction isn't for sending someone money or utxo consolidation, then it's a bad utxo, even though it's no different from any other clean utxo, if not cleaner in comparison to many other utxo because no op_return rule + input=output, as in as legit/greenlight of a bitcoin transaction as it can be". I was wished upon that I'd stop doing DNN because of this perceived threat that's supposedly bigger than ordinals and op_return (combined?), but wtihout coming to understanding how this is that big of a threat, if a threat at all, I probably won't... ...not out of being malicious, as I'm simply solving the ID and DNS problem with it, as effeciently as possible, and as cost-effective and cleanly cleanly as possible, and the most simplest with the highest security possible, and there's no one backing me, and I won't be getting anything out of this aside from using it like everyone else, so there's no conflict of interest or ulterior motive (not saying anyone is saying that, just trying to deliver a point, which is...), so since I can't see or understand the problem, then I can't even agree or disagree if it is a problem or not to then decide if i'd continue making DNN or not, as a result i'd continue making it. From my point of view after thinking about it, the pushback isn't a protocol purity resistance (resistance against op_return/junk, witness exploitation, etc, which is a legit pushback and I resist it as well), but rather a hyper purestic ideological that extends/overeaches outside of bitcoin. Going back to what Satoshi mentioned about this topic, where one or more people asked about adding a DNS solution into Bitcoin, the idea was rejected and suggested that a DNS solution should be on a different chain, so that no non-bitcoin/transactional data is added to Bitcoin, and as a result namecoin and others like it were born, however, the discovery with DNN is that it follows that exact logical reasoning: nothing is added to Bitcoin (no spam/junk/bloat), and DNN only observse it (observes only clean transactions). If there was such a thing like a 'Satoshi Test', then DNN passes it with flying colors. When I think about my opinions on Bitcoin in regards to what should be done with it or what shouldn't be done with it, the line is clear: don't add unrelated things to it (op_return, witness exploit, ordinals, etc), don't overreach (prevent people from doing a normal utxo because of a disagreement on the why, which is more dangerous as that would add subjectivity to objective system). However, I might have gotten something wrong or am fully delusional, so if you have thoughts, feel free to share it.

The New Zealand government sent DEG Mods a takedown request of a game mod post through Namecheap, with a threat of legal proceedings of sorts, which may result in Namecheap suspending access to the DEG Mods domain address. Good thing DEG Mods was built on the awesomeness of nostr, and good thing that something like DNN was figured out developed, and with a good push to have browser parterships, there wouldn't worries about having your domains be unjustly shut down anymore or stolen from you