> For the complete documentation index, see [llms.txt](https://whitepaper.dm3.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.dm3.network/abstract.md). # Abstract *DM3 is a web3 messaging protocol focused on security, decentralization, privacy, scalability, and interoperability. It is based on a decentralized network of message relay nodes and a standardized registry for communication profiles rooted in ENS (Ethereum Name Service). DM3's interoperability approach enables the connection and integration of different systems and the establishment of an interoperable, connected messaging ecosystem without compromising existing solutions' security, privacy, and UX.* *Building on the lean core protocol, modular extensions provide solutions for many messaging applications, including outstanding spam protection, integrable components to easily integrate messaging functionality into apps, enhanced privacy, and much more.* *The DM3 utility token powers token-based functions (such as spam protection, incentivization for privacy functions, etc.) but also serves as a governance token and incentive for standardization.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://whitepaper.dm3.network/abstract.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.