> The end goal is native support and or native browser integration. Did you happen to see the demo video for the browser I made? It does this. > Also all naming systems introduce another issue of an oracle that can lie (or require KYC) in a similar way that DNS does. What I designed is a protocol. There’s no KYC anything. It’s just first on chain gets the name forever unless they trade it. Don’t need to overthink the trading part either. Here’s the specific part of the README that covers it:

GitHub

GitHub - btcjt/titan: A native nsite:// browser for the Nostr web. Named after Titan, moon of Saturn.

A native nsite:// browser for the Nostr web. Named after Titan, moon of Saturn. - btcjt/titan

> Anyways, I'm not convinced it will work. But I'm willing to be proven wrong I’m not sure what the concern is with it. There’s no central issuer or anything like that. Anyone can scan the blockchain for an “NSIT” op return to see what utxo controls a name and what npub the name points to. I think there’s something here. Even without the naming convention I came up with.

Native support is just code for corporate takeover, courtesy of the W3C and ICANN cartel.

Naming issues are complex, blockchain can help, but native integration is key.