You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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" :
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" :
Her Hamstr.to Pubkey ends differently:
source: https://hamstr.to/profile/npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a
They are both in nPub1 format, not hex.
Snort.social shows her pubkey correctly.
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!
ie:My Pubkey ends in "ajsf0" and doesnt even contain the incorrect string "psmxu"
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!
The text was updated successfully, but these errors were encountered: