True, though that’s a bit more centralized albeit possible.
Discussion
Actually in the original/current NIP-05 spec but was ditched. https://github.com/nostr-protocol/nips/blob/master/05.md
Can be improved like you can have alt DNS servers. Just a matter of definition. Could be just file-hash pointers but there needs to be some point of entry to start the query.
Hmm what about NIP-05 with decentralized DNS? I think ZeroSync will enable that on bitcoin without needing to be a full-node, but we could test it with namecoin in the meantime.
The relay IP hosting the NIP-05 data can be updated on-chain. When you connect to it, you download the user’s list of currently selected relays.
A user could put this decentralized DNS in all their notes. Could even have two or three decentralized DNSes and put all of them in every note you post.
Downside is the user has to buy the domain and pay to update the IP when needed, but it does feel more intuitive at least.
What's wrong with using blaster for relay list replacable events per the gossip model? Why the need for on-chain data?
The issue is relying on relays to propagate your NIP-65 note to ALL other relays. It might not propagate to ALL of them if you’re just trusting it to propagate. Negentropy with interval-based syncing will help though, which were coding in Go.
The blockchain OTOH is the ultimate central repository (that’s ultimately decentralized) that any relay can use to check which relays you’re committed to.
I think Gossip is a great start that doesn’t use on-chain data. Just saying, if we want to take it farther there’s a way to do it without needing to pay on-chain fees everytime you post. The blockchain is valuable if it can be made cheap for users.