# SafleID

User adoption and onboarding have been persistent challenges for blockchain-based applications, commonly known as dApps. One of the primary obstacles is the complexity associated with storing and managing public addresses, which serve as the main identifiers for users. This identifier is used for all chain based interactions, asset transfers and discovery. Unlike traditional applications, where user management is straightforward and intuitive, the necessity for users to handle cryptographic keys and public addresses significantly hampering user retention in dApps.<br>

Existing solutions like Ethereum Name Service (ENS) and Unstoppable Domains offer domain services aimed at simplifying user interactions by mapping human-readable names to public addresses. However, these services are limited in scope. They primarily focus on address discovery and do not provide a permanent association with a single public address which is basically the wallet for the user. This limitation can lead to scenarios where funds are sent to expired domains, resulting in potential loss of assets.\ <br>

<figure><img src="https://3923746849-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGG017pljpan7LWSR28t9%2Fuploads%2FdztBh5d86YlO1DqiCS5v%2Fimage.png?alt=media&#x26;token=c83b452d-0f89-4ee7-b1e1-41cfe296828e" alt=""><figcaption><p>Navigating multiple blockchain addresses can be confusing</p></figcaption></figure>

{% hint style="info" %}
**The lack of perpetual linkage between domain names and public addresses introduces a critical flaw in user experience and security.**
{% endhint %}

There is a pressing need for a more robust infrastructure that not only simplifies user interactions but also ensures persistent and reliable public address management.


---

# 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://docs.safle.com/safleid/safleid.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.