Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report: Pubkey is not displayed correctly on profile #45

Open
Marc-Gee opened this issue Feb 19, 2023 · 0 comments
Open

Bug report: Pubkey is not displayed correctly on profile #45

Marc-Gee opened this issue Feb 19, 2023 · 0 comments

Comments

@Marc-Gee
Copy link

Hi,
I accused a nostr profile on Friday of being an imposter because her Pubkey didnt match to the genuine users [twitter] verification post, nor the nostr directory entries. However, it is I believe a Hamstr bug actually. .
I discovered afterwards that my own pubkey on hamstr.to has the same issue. The beginning is correct, but the end characters are not!

As the example - The correct, verified, published npub1 key of Lyn Alden ends in "cw83a" :
Screenshot LynAlden - Verified Pubkey

Her Hamstr.to Pubkey ends differently:
Screenshot LynAlden - incorrect Pubkey showing
source: https://hamstr.to/profile/npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a
They are both in nPub1 format, not hex.

Snort.social shows her pubkey correctly.
image

same issue exists with my pubKey also. and that is when I realized Lyn was not an imposter, but rather my client was giving bad output!
image
image

ie:My Pubkey ends in "ajsf0" and doesnt even contain the incorrect string "psmxu"
image

Please can someone verify if i am doing / seeing something wrong? Accusing the authentic user of being an imposter, Wasnt fun.
Lyn Aldens verification post is here: https://twitter.com/LynAldenContact/status/1626654795606986773

Thanks for your excellent nostr client!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant