Users Can Now Use their Ethereum Addresses to Forward Emails

News • 2020/09/20 • by
remitano

A new feature has been brought forward by Unstoppable Domains that allows any person who has a domain with a .crypto extension to forward email signed by the Ethereum private key that secures it. This tends to remind us of the way ancient cypherpunks utilized PGPkeys in signing their emails.

Bradley Kam, co-creator of the technology firm, informed Cointelegraph that the email service "unstoppable email" is issued via ETHMail webmail, and it is not decentralized. According to Kam, the service will be available without charges, and having a .crypto domain to forward emails is unnecessary. Another advantage of using this feature is the assurance that the email comes from the specific domain owner since the email is signed with a private key.

The feature is a new course of action towards the extensive decentralization of the web, says Kam. A decentralized chat known as dChat was released by the firm recently.

Ethereum has over a hundred million addresses, and as each day passes, new addresses are included. Nevertheless, if the need to provide a solution to spam (from Ethereum-based emails) arises, a remedy originating from Adam Back, a crypto pioneer, is available. The Hashcash he built was explicitly to stop spam. Some other digital currencies, including Bitcoin and Ethereum, approved this concept after an email-sender provided proof-of-work for the outgoing emails.

Source: Cointelegraph

Comments (5)
Guest
freshprinx
6 years ago
Cool stuff
exodusab
6 years ago
hmm, new adventure
lorettachinasa
6 years ago
Interesting
visiblemoney
6 years ago
Having the email innovations centralized is a flaw. I think they should find a way to decentralized the email protocol to be on the same page with the consensus of Crypto ideology - decentralization.
paulsmith2018
6 years ago
Nice one But it should be decentralized please..
User rewards

Our newsletter

The latest cryptocurrency market news, technologies, and help resources.
[Error] You have exceeded number of allowed requests for this action