Hey, to clear something up; getting a NIP-05 'verification' has nothing to do with your nsec. (If you ever needed to give your nsec for a verification to anyone consider your account lost)
About NIP05:
Your account is made with a public key, which is very long and confusing. In order to make 100% sure you are talking with the person you think you are, you should check the npub key. Dont trust, verify, right? To help in this process there is the NIP05 verification. Your npub is made simple; kinda like an email-address, easy to read and fast to check.
Because your npub is linked via a domain to your NIP05 the client you are using will do the npub check. Only the owner of the account with the linked NPUB will show a valid NIP05, any other account will show it as invalid.
To clarify; This isnt linked to twitter, your profile name, your email-address or anything like that. Really just a way to make your npub easier to check and to see a nice checkmark in most clients. Your npub is never needed for this proces. All the provider needs to do is convert your public npub into the hex variant and add it to a file on their domain.
You are in control to use it, as you are the only one who can edit your profile and set, edit or remove the NIP-05 part.
Also: The NIP05 is very easy to automate and can even be done with free domains, so in my view in no way a valid anti-bot method.
Nostr-Check.com
npub1mh…v9a4h
2023-03-29 17:11:57
in reply to nevent1q…0qf7
Author Public Key
npub1mhamq6nj9egex0xn0e8vmvctrpj0ychehddadsketjlwl3eg7ztqrv9a4hPublished at
2023-03-29 17:11:57Event JSON
{
"id": "0d21c841be708bc806eede400ba068c3ac87f461d7bd46a816a7ff92da1a9ebf",
"pubkey": "ddfbb06a722e51933cd37e4ecdb30b1864f262f9bb5bd6c2d95cbeefc728f096",
"created_at": 1680109917,
"kind": 1,
"tags": [
[
"e",
"eb492465a037a58d43026e3c422b076e5c7c304a7fb01e9418cfff4cecf65e60"
],
[
"e",
"dcd17a3de608d2029416d5ebaac9894b19107c1eb150f8139991744015b0527d"
],
[
"e",
"dfde8309d19b92272192d6a60874e24f0aaf54002522e2a3cd73d0c728b644c6"
],
[
"p",
"fb4053b9cbf26498997f1ee181329a9d7976d43241d2841746970fe79e06ef07"
],
[
"p",
"ae668387f74ff3dabf1c8ffa99bb53758d00d179533d7113d5f8b5d2ee570f6d"
]
],
"content": "Hey, to clear something up; getting a NIP-05 'verification' has nothing to do with your nsec. (If you ever needed to give your nsec for a verification to anyone consider your account lost)\n\nAbout NIP05:\nYour account is made with a public key, which is very long and confusing. In order to make 100% sure you are talking with the person you think you are, you should check the npub key. Dont trust, verify, right? To help in this process there is the NIP05 verification. Your npub is made simple; kinda like an email-address, easy to read and fast to check. \n\nBecause your npub is linked via a domain to your NIP05 the client you are using will do the npub check. Only the owner of the account with the linked NPUB will show a valid NIP05, any other account will show it as invalid.\n\nTo clarify; This isnt linked to twitter, your profile name, your email-address or anything like that. Really just a way to make your npub easier to check and to see a nice checkmark in most clients. Your npub is never needed for this proces. All the provider needs to do is convert your public npub into the hex variant and add it to a file on their domain. \n\nYou are in control to use it, as you are the only one who can edit your profile and set, edit or remove the NIP-05 part. \n\nAlso: The NIP05 is very easy to automate and can even be done with free domains, so in my view in no way a valid anti-bot method.",
"sig": "3dcacd64c43b5d2531ea5fd8aa42b7fb54b9b51e9776e8b6074de88c9ff9e21638a1e5f84dcbb6831910ba486ce7b9b5a8175d4222742009934d5472402ce1cb"
}