 Hello, my name is Heiko, I'm a developer at Corpus Ventures and I'll present you now DM3. What is DM3? DM3 is a simple protocol for messaging, it's decentralized, it's open and it's secure. To achieve this, we built DM3 on established web-free protocols like ENS. The properties I just mentioned make it sensitive, resistant, we designed it so that there's no single point of failure and with DM3 users are in control of their data. Everyone can write an own implementation of DM3. The basis for DM3 is a registry where users can store their profiles. We used ENS text records for that and on the middle layer we have the delivery services, buffer the messages until they are delivered to the messaging app. On top you can see the messaging app. Since the registry is the core of the protocol, I'll now explain a little bit deeper how it works. As you can see, we have the public encryption key in the text record for the profile and also the public signing key and also important is the delivery service name, so there must be at least one name of a delivery service. The delivery service text record also contains public keys and it contains a URL. This URL is pointing to the delivery service instant where messages can be sent to. It's also possible to store data off-chain or on layer 2 by using CCIP. This allows the creation of DM3 profiles without 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. This slide shows how a message would be delivered from Alice to Bob. So at first Alice types a message into the app. Then the app will retrieve the DM3 profile of Bob which contains the delivery service name he is using. In the next step, the app will retrieve the delivery service text record where there is the URL of Bob's delivery service. Then the message is signed and encrypted and sent to Bob's delivery service. The delivery service will push the message to the app that will be decrypted. And the app will look for the profile of Alice and that's needed because the signature needs to be checked. And if the signature is fine, Bob can then read the message. Besides the protocol definition, we also have a reference implementation. The reference implementation consists of four different packages. We have the DM3 web app. As you can see, screenshot here on the left side. It's also online available on the app.dm3.chat. Besides the web app, we have the React package. This can be used to include a widget of DM3 into other apps. And then we have the back end package. This contains the delivery service. And finally, we have the DM3 lip which contains basic protocol services. So we are working also on protocol extensions which take care of things like group messaging. These extensions are optional. If you want to write a DM3 implementation, you only need to follow the DM3 message transferred protocol. So that's our roadmap. Until now, we published the protocol draft and the reference implementation. A critical goal of DM3 is to enable interoperability between currently isolated Web3 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 implementation. Yeah, if you want to include DM3 into your app, let us know. We'll try to support you. That's it. Thank you.