The dm3 protocol is a minimum viable messaging protocol, utilising a general registry for public keys (encryption, signature verification) and delivery information based on ENS (e.g., ENS text record eth.dm3.profile) and decentralised delivery service nodes. Intended to work as interoperability layer, dm3 enables various dApps/protocols/services to exchange messages in a standardised way.

On August 22nd, we presented the dm3 Protocol to the ENS Community (https://discuss.ens.domains/t/dm3-decentralized-messaging-for-web3/14090).

The dm3 protocol since then has been building a specification based on community feedback, as well as reaching out to other messaging apps/protocols in order to find alignment with key members of the messaging ecosystem.

On November 16th, we presented the latest version of the specification (v0.3) that can be read here: https://dm3.readthedocs.io/en/doc-latest/specification/message-transport/mtp.html, we also shared on the ENS Forum, the specification as well as a roadmap for the protocol, any comment or feedback can be done here: https://discuss.ens.domains/t/standardization-web3-messaging/15182 or directly as pull request in the github repository: https://github.com/corpus-ventures/dm3-spec

With this proposal we are seeking to support the coordination efforts on the way to standardisation or contributions done by members of the ENS community to the dm3 protocol.

Our DMs are open!