Thread

I always wanted to have sovereign domain names with the UX of phone numbers; - can I have your domain? - sure; it is O4DK, SFBQ! *Writes*: o4dk_sfbq.mns.alt #WIP (unless I discover a fatal design flaw) #MNS

Replies (17)

As a nostr user, I like that I can use as many npubs as I want. Throw-away npubs are very useful for testing. And having different profiles/npubs for different contexts and applications is also very powerful. Being accountless makes trivial to generate and use several npubs. I'm guessing how this could change with a much "reduced" namespace. Ok the other hand, what feature could be implemented in domain assignment in order to protect against bots saturing the namespace?
1. These are not mutually exclusive, not any more than DNS and IPv6 are. Your protocol should support MNS and Pkarr/Npubs ... One for throwaway accounts and one for stable identity. In fact Nostr already have Nip05 ... I just want to make that sovereign. 2. You touched on one of the two main problems my design needs to address. But it is actually the simplest of the two; you make it computationally expensive to create these Names, just enough so that a user can do it once with ease, but millions of bots break the bank, and you have trillion names so even millions of bots won't saturate it. I will share the actual details once I have working prototype instead of just making promises.
1. Ok, I understand now. It's a NIP-05 improvement making it sovereign. πŸ‘ I dislike NIP-05, though. Some people misunderstood it as the identity itself, when it really is a DNS alias for the npub, as in nostr the identity lies on the keys. I think it's more dangerous than useful, tbh. 2. Ok, PoW then. πŸ€™ Looking forward to read the details! Thanks for your answers. πŸ«‚
NIP-05 is useful *just* for corporations that already have an already established and known DNS domain, as they can use it to "announce" their official npub. But NIP-05 has no use for individuals without an already existing and well known DNS name. Some nostr clients presenting every profile with NIP-05 as some kind of "verified profile" are just messing around and misunderstanding NIP-05 utility. Impersonators could very easily define any NIP-05 in order to show as verified and try to deceive people.