The mission of dm3 is not to replace but to connect. As layer-0 messaging protocol, dm3 enables other messaging protocols, services, or app to become interoperable with all other dm3 compatible solutions without compromising security or privacy.
Yes. The dm3 embedded components can be used to add secure dm3 messaging to any dApp.
No. End-2-end encryption is an essential feature of the dm3 protocol. If supported by the sender’s and receiver’s client, a different encryption algorithm could be used. ATTENTION: the use of not secure encryption schemes is not recommended!
No. The dm3 protocol is blockchain agnostic. Even if it uses ENS as general registry for dm3 profiles, any other source (L2s, other chains, cloud services, identity providers, …) can be used as well. By linking these sources to ENS (via CCIP) a generalized access is possible.
Beside Ethereum and ENS, Layer-2s like Optimism (and any other Optimism based L2s like Base), Arbitrum, BNB, Gnosis Chain and cloud-services are possible. Prototypes are implemented for Optimism, Base, Gnosis, Cloud-Services. PoCs exist for BNB, Arbitrum, Mantle. More to come!
