Closed chadyj closed 5 years ago
oh and one more thing....
Issue is caused in status-react when resolving pubkey x = 0 and y = 0. When both are 0, it should not continue, perhaps show an error message
@3esmit actually this is not the problem, the problem is that the chinese guy registered c
(https://etherscan.io/enslookup?q=c.stateofus.eth) so that name was resolved and since carl
doesn't resolve to a valid address, the resolution of c
to the public-key of the chinese guy was staying in the app state. I fixed the input so that now resolution of a shorter username is discarded as soon as you add additional characters in this PR https://github.com/status-im/status-react/pull/6537
Still having this issue on desktop, when I enter carl
or bruce
, for example. It should be fixed in the desktop builds right @yenda?
carl
doesn't resolve for me either because it isn't associated with public-key, but bruce
does
bruce
is also working for me this morning 🤷🏼♀️
By now everyone has heard the story of trying to chat with
carl
and getting a random Chinese dude! There was much laughs at the thought of a squatter.But after digging deeper it looks like that Carl registered his name but for the contact code wasn't captured.
So we have these potential issues:
Contact code potentially not saved (Carl thought he did, but isn't 100% certain)
carl
resolves to0x04ee8c9662467fbce7398d5d9591a5b3657ba6f487bdfc33dd6d053d6252b36ba09b9d9cba387ab267e607807709195135fca1ccb8a81a6931ee67079975f9091c
, but it shouldn't resolve at all since there isn't a contact code saved (see screenshot above or search forcarl
in the dapp)Can we verify #1 and also fix the issue when we resolve incorrectly?
cc @rachelhamlin @3esmit @bgits @yenda @naghdy