> 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/all.id-components.md).

# All.id components

Page actionsAll.id network architecture is composed of three main components, the discovery server, the router and the peer. First we give a brief description of each component, then discussing the process of authenticating a new peer in the network, and at last detailing what components belong to a peer.Comment

### How does the All.id work? <a href="#how-does-the-all.id-work" id="how-does-the-all.id-work"></a>

CommentAs a platform DLT based, All.id is a kind of digital database that is updated and held by every member(peer) independently in a large network.CommentThis way of operating is as revolutionary as it is easy to understand. While traditional solutions send requests and store all assets in a single database, All.id distributes the storage and, consequently, the requests to the databases of the network members (peers). Basically, All.id consists of three components:Comment

#### Discovery server <a href="#discovery-server" id="discovery-server"></a>

CommentThe discovery server is one of the most important network components, begin responsible for authenticating new peers, keeping a global history of network transactions, validating all carried out transactions and guaranteeing the integrity of network resources and communication.Comment

#### Router <a href="#router" id="router"></a>

CommentThe router is mainly responsible for intermediating the communication between network peers, acting as a literal router for requests and making external queries, outside of the All.id network, if necessary. It can act as a logical separator in the network, where each router completely isolates a group of connected peers from the rest of the network.Comment

#### Peer <a href="#peer" id="peer"></a>

CommentThe network main component, it's used by All.id clients to interact with the network ecosystem created by All.id. This component contains all information and functionality needed by clients to allow Requests in the All.id network.


---

# 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://docs.caf.io/caf-docs/user-guide/resolution-6/all.id-components.md?ask=<question>&goal=<endgoal>
```

`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.