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