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.

In addition when I try do the initial connecting #Warpcast to my eth address, it pulls up ChristopherA.eth, which it should not. #Warpcast should not use the ENS reverse as it is not authoritative, it should first confirm that the ENS name is controlled by the eth address.

Your primary address still has Christophera.eth set as the reverse resolve for https://etherscan.io/address/0x3393f9e8306f51754e3d6ca296d01d354da73ca9
You can change this on app.ens.domains

Software Engineer @ Cadence Design Systems. B4: Stanford EE / Illinois ECE

I do not own ChristopherA.eth, it was poached, and thus I can’t change it. I personally consider it as a critical bug that you don’t confirm first that my eth address still controls it.

They have the link to me at https://app.ens.domains/name/christophera.eth/details

I was able to do this here.

Still feels concerning that the app doesn’t check that the ENS name is still controlled by the key.

From your 0x333 pubkey, you just need to hit the trash button and sign the txn: https://i.imgur.com/zdbI9ZB.jpg