Christopher Allen
@christophera
Serious glitch in #Warpcast signup. I gave it my eth address, but that address does not hold ChristopherA.eth (it was poached) but that name has a reverse lookup to my address, which the holder of that name does not have access. #Warpcast apparently wants a signature of the poachers eth address, not mine.
2 replies
0 recast
0 reaction
Vinay Vasanji
@vinayvasanji.eth
@dwr.eth @v can you look into this?
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
hmm, i may need more details to debug this. this is odd because: 1. we don't ask for any particular eth address, you choose which one you give us. 2. it doesn't look like you connected an address, so im not sure what you mean by "we show you as having christophera.eth" do you have a screenshot you can share?
1 reply
0 recast
0 reaction
Vinay Vasanji
@vinayvasanji.eth
I suspect its because christophera.eth maps to Christopher's actual Ethereum public key. But the .eth name is controlled by a squatter. FCs onboarding logic assumes that if the resolver is X the controller is also X-which is not the case here.
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
warpcast's onboarding doesnt do anything with showing or requesting ENS names afaik
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
the only place where we show ENS names is if you successfully verify an address that is the ownerOf an ENS name, but I don't think chris completed that step from what I can tell. a screenshot with the incorrect ENS name showing up in the Warpcast UI would be tremendously helpful for debugging.
1 reply
0 recast
0 reaction
