> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-docs/user-guide/resolution-6.md).

# Resolution 6

All.id is a distributed network built upon a peer-to-peer protocol using DLT concepts for storing and processing digital identity data.

#### Market context <a href="#market-context" id="market-context"></a>

In a digital first economy, identity is built on data and data drives all business decisions. The ability to harness and analyze the data effectively is more important than ever. However, as data becomes more valuable, businesses are having to spend more and more money as: Fraud continues to grow in size, volume and complexity as fraudsters look to harness and monetize stolen credentials; Countries across the globe are implementing regulations to try to create ways to protect users/data usage. This is further increasing the fragmentation as businesses try to serve a global customer base; Global expansion requires the need to add new and disparate data sources.

All this has created identity as an industry where vendors compete to gain access/control of the data and then monetize them at the expense of the businesses they serve.

#### Identity redefined <a href="#identity-redefined" id="identity-redefined"></a>

We believe that the solutions based on traditional centralized data models are ineffective and there is a need for a layered approach to identity security and validation.

All.id is the world’s first decentralized identity network created to revolutionize compliance and fraud prevention in a democratic and secure way. It is built on the principles of Distributed Ledger Technology (DLT) with a mission to provide a solution that is faster, more accurate, safer and cheaper than existing ones in the market. Some of the key advantages of All.id include:

* **Privacy first approach:** The network is composed of a series of nodes capable of securely sharing customer insights (biometrics, devices and other attributes) without burdening the privacy of individuals or companies;
* **Decision accuracy:** The decentralized approach ensures higher accuracy by cross-referencing across the nodes;
* **Future-proof decisioning:** Customers can share layered insights across data elements (without sharing data), leading to better decision-making. It also ensures that the network self-heals by actively watching all transactions and identifying potential problems and outliers at runtime;
* **A true collaborative identity network:** Redefining the identity to enable you to deliver the best experience and security to your users;
* **Data ownership:** You are the true owner of the data, and we don’t monetize your data against you.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.caf.io/caf-docs/user-guide/resolution-6.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
