Hey thanks for pointing to this. NIP65 is definitely part of the solution -- it's the (signed) thing that you want when you have an npub and are looking for its relay.
But relays don't talk to relays, and even if they did it isn't practical for every relay on the planet to store the latest NIP65 for everynpub on the entire internet. Even if this were possible, it would cause awful spam attacks.
I think the solution is coming into focus: I knew the DHT keys would be npubs, and now you've pointed out that validly-signed NIP65 kind:10002 notes should be the values.
Exactly, signed 10002 events. Spam can be mitigated by requiring payment or proof of work on the event. Relays are starting to talk more to each other, many are using the negentropy protocol to sync
npuband are looking for its relay.npubon the entire internet. Even if this were possible, it would cause awful spam attacks.npubs, and now you've pointed out that validly-signed NIP65kind:10002notes should be the values.