# Linked Profiles (DM3LPP)

## Overview

For certain use cases, standalone (or anonymous) profiles that can optionally be linked and synchronized with the main profile are required. For example, a dApp could provide integrated in-app messaging, a website could allow direct contact with designated persons, or a billboard chat allows anonymous users to post statements. These functions can, for instance, be realized using the embedded **dm3** components.

Eventually, it might be desirable for users to connect to a dApp without disclosing their identity to send messages anonymously. Users should also be able to write a message from the embedded messaging widget independently of their messenger app, which is then optionally synchronized with their inbox.

In addition, security considerations may require using limited-scope profiles with restricted rights derived from the user's wallet, which should be linked optionally to the user's inbox.

*The following description refers exclusively to ENS as a registry but can equally be applied to any other name service of any chain or layer 2 or even a cloud service.*


---

# Agent Instructions: 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:

```
GET https://specification.dm3.network/protocol-extensions/linked-profiles-dm3lpp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.