How might .eth names be used for instant communication or email in the future?

Does anyone have anything that they can share related to how .eth names may be integrated with chat/messaging tools or email capabilities? It seems inevitable that if an .eth name is your identity that can be brought with you anywhere in Web3 that there should also be an easy way to communicate privately beyond discord or twitter? Can someone share some developments that are happening in this space?

4 Likes is already using ens names for email. The experience is a bit clunky but I know they are working on enhancements. You can use the service without giving up any personal info which is nice.


Thank you for sharing this! I am interested to see how many more will pop up and win in this space.

I should also mention which has made great progress towards decentralized notifications. In fact, I believe the service could be used to notify when ENS names get close to expiration. EPNS could potentially be a key foundational building block of web 3 just like ENS. I am not an expert on the service just sharing my initial understanding.


This is also helpful thank you!

One more…I just learned of the inb0x project. It allows use of ens to send emails as well.
Engineering inb0x. End-to-end encrypted wallet-to-wallet… | by Parallel | Parallel Life | Dec, 2021 | Medium

1 Like
We should do our best to make a similar project based on our domain name

@slobo.eth is hard at work on a chat application, care to share any details?

will be sharing this more broadly in 2 weeks working out the final bugs. will post an update in this thread as well.


The Status apps have (and have had for a long time) ENS integration.

For example, you can message/mention me using michaelb.eth.

A few things to note if you decide to try out the apps:

The desktop app has been undergoing a massive refactor since the latest beta release, so I’d recommend cloning the repo and building the default branch vs. downloading the pre-built app, though it requires a fair bit of dev tooling to be installed and familiarity with command-line tools, e.g. make.

Both the mobile and desktop apps are in the process of transitioning to communities focused messaging. The public chat system that’s been in place from the early days of Status has long been plagued with spam. It’s still usable, though, and if you start a public chat with an unguessable component in the name (e.g. ourchat-ec1ef74) it will be unlikely to get spammed if you share the name discreetly.

[ disclosure: I’m a core contributor at Status, but am not a member of the mobile/desktop app teams ]

I tried out status and it was spam city. I haven’t heard much about their development recently. Do you have any information you can share here?

[disclosure: I’m building a competitor]

The sentences I wrote following the one you quoted provide info and links to info re: Status’ efforts to move forward with a communities focused messaging platform, and how that relates to the spam problem.

Status is also behind Waku Connect, which builds on the Waku network. Status’ mobile and desktop apps also build on top of Waku, which is the underlying communication protocol. Technically, Status messaging (including the spam-prone public chats) is an application on top of that protocol. The goal of Waku Connect is to make it possible to leverage the protocol in other contexts, e.g. dApps running in browsers as independent applications of Waku, i.e. independent of the Status messaging application (which is just an app using Waku).

Best wishes re: your project, the more the merrier in this space!

1 Like is using .eth names for encrypted DMs. Since it’s running on permissionless Ceramic Network there is no platform lock-in either.