Ok thx
Discussion
Ok so I looked and the method I’m proposing would totally work in this case.
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s would add a TXT record to damos.io with his npub and any clients to that built in a lookup would know which one was fake and which one was real.
nostr:npub1elwpzsul8d9k4tgxqdjuzxp0wa94ysr4zu9xeudrcxe2h3sazqkq5mehan
How would it work with other fake accounts? For example, a celebrity creates a real account. Then someone creates a fake account. How would we know which one is real and which one is fake?
The celebrity puts a TXT record in their domain name which is in their profile - the imposter also puts the same domain in their profile (they always do )
The domain tells the client what the true npub is for that domain - when I wrote the original article we released a proof-of-concept chrome plug-in that shows the concept in action
https://easydns.com/blog/2022/08/05/solving-the-fake-twitter-profile-problem-with-dns/
nostr:npub1elwpzsul8d9k4tgxqdjuzxp0wa94ysr4zu9xeudrcxe2h3sazqkq5mehan Wow. Impressive. 👏
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s Thoughts?
this is what nip05 is for except it uses https instead of dns and already built into every client
The fake @jb55 could still stand up a valid NIP-05 using a different address and then put your domain in the profile.
That’s why you need the triangulate with the DNS TXT record (in a way, this is a continuation of the argument I’ve been having with nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 for nearly a year except I hadn’t thought of the fake Nostr handle issue until now. )
FYI we met very briefly at Bitcoin 2023 and I was going on about adding NIP-05 npub to DNS then.
