> For the complete documentation index, see [llms.txt](https://fabco.gitbook.io/dappy-spec/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fabco.gitbook.io/dappy-spec/glossary/multi-request.md).

# Co-resolution

A co-resolution (or multi-request, or trustless lookup mechanism) is the operation that a client performs when he queries at least two members of a given Dappy network to read something from the blockchain. It is the main operation at the core of the dappy paradigm.

By doing a multi-request instead of a unique client-server request, a client is able to read from a public database that he does not have locally (the state of a blockchain), without having to trust any single entity. Multi-requests in Dappy are a sort of trustless remote database query mechanism.

![](/files/-MhKJ7LMqttofBr-h9s1)

When a client receives response from a multi-request (ex: AAAAABA), he can apply arbitrary consensus rules to accept or reject the result (sometimes called synchrony constraints also). The client may require 100%, 90% or 80% of identical responses. He may also require that a maximum of 2 groups of different answers.

![](/files/-MhY8l8mJMuB2-kVgMBl)

**Example:** In all releases of dappy, the list of the names is recovered by asking all the members of the Dappy network and requiring 100% accuracy (all the responses must be the same).

The library [bees JS](https://github.com/fabcotech/beesjs) is currently the library that handles the co-resolution and reconciliation, it is used by dappy browser (web browser) and dappy lookup (node JS).


---

# 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://fabco.gitbook.io/dappy-spec/glossary/multi-request.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.