Ethresear.ch: email login will be disabled in 7 days

[hwwhww]

@axic

I see. But wouldn’t it be possible to add a field for “ENS name” in discourse (like now there’s the email field + github link) so the linking happens?

I believe we can add ENS name (or, ETH account) field in discourse. And then, we need to ask the GitHub login user to manually update that field to claim that “the one who has this ENS name / ETH account is me”. So when the user uses Eauth login later, it will be able to bind to the existing account.

@axic

Alternatively (though I am not a big fan due to the privacy aspect) EIP-634 could be used to link an ENS record to an email.

Right, adding the email field in ENS can also solve the password recovery issue on discourse! I understand why we may be against it, we are trying to dogfood with a decentralized solution, but we still want the email system to prevent a user from losing their properties forever.

@vbuterin

By ENS transfer you mean what happens if an ENS name is transferred to another account?

Yes.

@vbuterin

Wouldn’t the natural answer be “well, for future logins start verifying signatures against that new account instead of the current one”? What’s the problem?

I think the authentication follows the authorized controller of the ENS name, and use ENS name as the default handle name? It doesn’t take ENS as the first-class when searching for an associated account (ping @Ping to verify it).