The pubkeys should be in hex format, not npub. It looks like some clients are gracefully handling it, but you may experience issues with some clients.
https://github.com/nostr-protocol/nips/blob/master/05.md#example
The pubkeys should be in hex format, not npub. It looks like some clients are gracefully handling it, but you may experience issues with some clients.
https://github.com/nostr-protocol/nips/blob/master/05.md#example
also, the names key should be just the username portion of your identifier with the domain being read from the actual domain used to fetch the document.
Oh, thanks! That was very helpful nostr:npub1g7ec7nfhyyus6kmtaaud4clnuwygandlrpz0hvem3pep6dndtjyqumtp42 !!
My keys were in the wrong format, so the proxies were also not being picked up.
With my current fixes I know #NIP05 is working because I could test it with the #coracle UI.
From my https://coracle.social/ profile page, I could click on the "Details" menu as shown here
https://void.cat/d/LqMc6vQkiuXA15tTzEGZU6.webp
and that opened the details page
https://void.cat/d/4RomLiFB3Wd512c52B47qu.webp
which matched my fixed nostr.json file
https://bblfish.net/.well-known/nostr.json
which I took a screenshot here:
https://void.cat/d/YCBKYZJRGfQS738vaTiXxx.webp
I guess I am wondering now if I have put too many relays in there, and if they are good ones. But that is another can of worms.