Ethereum Foundation DevCon 6 - Developer Infrastructure Track, 11 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: dm3 - Decentralized Secure and Open Messaging Protocol

Description

Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on Swarm, IPFS and more.
https://archive.devcon.org/archive/watch/6/dm3-decentralized-secure-and-open-messaging-protocol/

dm3 is a protocol enabling decentralized, open, and secure messaging based on established web3 services like ENS and IPFS. It doesn't rely on any central service. The user has complete control over where their messaging data is stored. By using ENS names and ENS text records as the registry for public keys, the user owns the identity linked to their messages.
dm3 comes with a reference implementation for a standalone web application, a widget, and a delivery service.

Speaker(s): Heiko Burkhardt
Track: Developer Infrastructure
Keywords: Messaging,open protocol,live demo

Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum
Learn more about devcon: https://www.devcon.org/
Learn more about ethereum: https://ethereum.org/

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.
Devcon 6 was held in Bogotá, Colombia on Oct 11 - 14, 2022.
Devcon is organized and presented by the Ethereum Foundation, with the support of our sponsors. To find out more, please visit https://ethereum.foundation/

A

A

I'm, a developer at Corpus, Ventures and I'll present you now dm3.

A

What is Team three team. Three is a simple protocol for messaging, it's decentralized, it's open and it's secure to achieve these people built dm3 on established. We have three protocols like ens the properties I just mentioned make it sensor help resistant. We designed it so that there is no single point of failure and with game. Three users are in control of the data. Everyone can write an own implementation of team 3..

A

The basis for dim 3 is the record registry where users can install their profiles and we used in as text records for that and on the middle layer. We have the delivery service, delivery services um buffer the messages until they are delivered to the messaging app, and on top you can see the messaging app.

A

Since the registry is the core of the protocol, I'll now explain a little bit deeper how it works.

A

As you can see, we have the public encryption key in the text record for the profile and also the signing public signing key and also important is the delivery service name. So there must be at least one name of a delivery service.

A

Okay, um the delivery service text record also contains uh public keys, and it also- and it contains the URL. This URL is pointing to the delivery service instant, where messages can be sent to.

A

It's also possible to store data off chain or on layer 2 by using ccip. This allows the creation of Team three profiles without a high transaction fees or if it's completely off chain, you don't have any, and it also makes it possible to include external public key databases.

A

This slide shows how a message would be delivered from Alice to Bob, so at first um Alice types, a message into the app, then the app will retrieve the team 3 profile of Bob, which contains the delivery service name. He is using.

A

In The Next Step, the app will retrieve the delivery service text record where there is the URL of Bob's delivery service.

A

Then the message is signed and encrypted and sent to Bob's delivery service.

A

The delivery service will push the message um to the app that will be decrypted and the app will um look for the profile of Alice and that's needed, because um the signature needs to be checked and if it's the signature is fine. um The Bob can then read the message.

A

Besides the protocol definition, we also have a reference implementation. um The reference implementation consists of four different packages. We have the dm3 web app as you can see the screenshot here on the left side, um it's also online available on the app.gm3.chat.

A

Besides the web, app, we have the react package. This can be used um to include which set of dm3 into other apps, and then we have the backend package. This contains the delivery service. And finally, we have the dim three lip which contains basic protocol services.

A

So um we are working also on protocol extensions, which takes care of things like group messaging. These extensions are optional. um If you want to write a team 3 implementation, you only need to follow the dm3 message. Transfer protocol.

A

So that's our roadmap. Until now we are published the protocol draft and the reference implementation.

A

A critical goal of Team three is to enable interoperability between uh currently isolated web history Messengers. We are now talking with many of those messenger teams to understand their needs and yeah. Please let us know if you want to join the discussion after we finish that process, we'll publish the specification and adapt the reference Implement implementation yeah.

A

um If you want to uh include team 3 into your app, let us know um we'll try to support you.

A

That's it. Thank you.