Nostr Web Client

What am I doing wrong here?

Trying to get NIP-05 verified with my own domain.

I've got the domain hosted.

I've got a .well-known/nostr.json file inside my public_html folder at my domain host. The nPub has been converted to HEX format using damus.io/key. The "name" I am using in the json file is GANDALF and then I am inputting gandalf@btcgandalf.com in the NIP-05 identifier field in my nostr profile.

I have followed the instructions to enable CORS by creating a .htaccess file.

But still no verification.

Any ideas where I am going wrong?

Reply to this note

Please Login to reply.

Discussion

Shawn 2y ago

You did it. It works. 🤙🏼

Shawn 2y ago

Weird. And now it’s gone.

corndalorian 2y ago

Interesting. I don’t see it in Damus. Would relays affect this?

Daniel aka Bitcoin Gandalf 2y ago

I've no idea. Do you know if my "name" field has to match my NOSTR username? I think I've tried doing "BTCGandalf": "hex npub" as well with no luck.

I was under the impression that the json file name would dictate what my "verified" name would be.

corndalorian 2y ago

I don’t know enough about how nip05 works beyond what others have already replied. Maybe the nostrplebs master himself #[3] has some insight? 😁

Carlos 2y ago

You only need to add the hex, not the npub.

Check out gigi's json: https://dergigi.com/.well-known/nostr.json

jamw 2y ago

Not seeing it in Damus yet either.

owenkemeys 2y ago

Hmm. Post your nsec?

LP Capital Chi 2y ago

When you figure it out pls share ser. Would like to use satspercuckbuck.com for mine

Tony 🥩 ⚡ 2y ago

I'm not familiar with that utility, but I'm showing your hex as :

ee0e01eb17fc6cb4cd2d9300d2f8945b51056514f156c6bc6d491b74496d161a

https://gateway.nostr.au/p/ee0e01eb17fc6cb4cd2d9300d2f8945b51056514f156c6bc6d491b74496d161a

Daniel aka Bitcoin Gandalf 2y ago

Yup that's what I've got

Sovereign Matt 2y ago

I remember having a similar issue but it fixed itself after a few days.

Daniel aka Bitcoin Gandalf 2y ago

Time heals all...maybe I will just leave it and see in a few days.

Disturbia 2y ago

Yeah its like that with some client.

jamw 2y ago

Sounds like you’ve done everything right - mine didn’t show up for a while though… a few mins. All I can recall is that some users kept the < > in the json file string which screwed things up.

Daniel aka Bitcoin Gandalf 2y ago

I'm gonna leave it over night and see. I knew to take the <> out. cheers

jamw 2y ago

I think don’t use the whole email as someone else highlighted.

jamw 2y ago

It’s snowing now in Damus! 🤙🏼

jamw 2y ago

And snowing I mean showing… 🤦🏻‍♂️

Kim Stock 2y ago

Merry Christmas

jamw 2y ago

Where’s the edit button? 😂

Ralphy 2y ago

It worked. I’m seeing you verified on iris.to

Tuvok 2y ago

i want to do that in future, but for me it has to be a little bit more easy. but own nostr veryfication would be my way. if you got it running you can get started to let others pay for that service! hope you get it done soon! ⚡👾🤙

Tony 🥩 ⚡ 2y ago

Remove the part highlighted

Tony 🥩 ⚡ 2y ago

Also might be case sensitive (not sure though). Try making the name in nostr.json match the case that you use in the profile field for NIP05.

jamw 2y ago

Yes this should not be there. Just use the bit before the @

Daniel aka Bitcoin Gandalf 2y ago

Yeah that was just me experimenting, it's back to just GANDALF and my NIP05 identifier is GANDALF@btcgandalf.com

hzrd149 2y ago

From the http response headers it says your using a platform called "hostinger".

If thats true this might help https://support.hostinger.com/en/articles/6320787-do-you-support-cors

There is a note at the bottom that says the .htaccess file needs to be at the "origin source" which im presuming they mean put it at "public_html/.htaccess" and not in the ".well-known" folder.

BtcPins 2y ago

This is what you need to focus on @npub1ac8qr6chl3ktfnfdjvqd97y5tdgs2eg579tvd0rdfydhgjtdzcdqnr657s

The headers is what was giving me issues with mine.

Daniel aka Bitcoin Gandalf 2y ago

I've got the .htaccess folder in my public_html folder so that should be all good unless there's something else wrong with it.

nostr.build 2y ago

Did you reboot?

nostr.build 2y ago

You can also try putting it in your config, .htaccess generally is not recommended unless necessary..

Daniel aka Bitcoin Gandalf 2y ago

Thanks - yup my .htaccess is in the public_html folder, not in the .well-known folder.

hzrd149 2y ago

Something else that might be causing issues is that your username is uppercase in the JSON file.

the NIP-05 spec says the name part of "name@domain.com" is case insensitive, but it dose not say anything about the JSON file.

If you look at https://nostr-check.com/.well-known/nostr.json all the names are lower case. I dont know if it will fix it but it cant hurt to copy what everyone else is doing.

Dries 2y ago

If your name is GANDALF, try using GANDALF@btcgandalf.com (case sensitive).

BaronBurdock 2y ago

Try using GANDALF@btcgandalf.com, I think its case sensitive

sondreolav 👀 2y ago

Write this in the .htaccess file:

Header set Access-Control-Allow-Origin "*"

And remember to use the hex version of your public key

Worked for me 😀