Email requires KYC, and if email is associated with an address, it will expose the user's identity information, which goes against Tari's privacy intentions

Email requires KYC, and if email is associated with an address, it will expose the user’s identity information, which goes against Tari’s privacy intentions

1 Like

valid argument! Yats could solve this

1 Like

Email doesn’r require KYC, :rofl:

1 Like

As long as there is an email that requires KYC, users cannot be allowed to take the risk of exposing their identity. Leaving the risk to users to control is foolish and goes against Tari’s original intention of default privacy.

While a given email may not have required KYC to attain it. Using the same email long enough will eventually make it a “KYC”.

I no longer use my Gmail account, since Google insists that I “2FA/MFA” using my phone number. While I refuse to my phone number for any form of security, I’m under no delusion that Google has already figured out what my number is.

I haven’t tried it lately, but I’m sure there is plenty of privacy violating information that can be found out about me by just doing a few searches based on my email alone. (including my phone number.)

Even if you find a random email generator, how will you use it? Have it forwarded to your main account? Or memorize (and login to) dozens, hundreds or thousands of emails for every different contact, that asks you for an email?

Not sure what good solution there is. Personally, I like Sessions solution. No ID, no password, just and encrypted key they issued. (But due to lack of support, they say they’re going away soon.) Honestly, I don’t know enough to say if it’s a good solution.